Enhance copy-armbian-kernel script to support copying U-Boot bootloader
packages in addition to kernel packages. Key changes:
- Add COPY_UBOOT flag (default: true) to enable/disable U-Boot copying
- Add UBOOT_SELECT variable for board/branch filtering (e.g., 'odroidm1:current')
- Split JQ program into reusable components (JQ_EXPAND, JQ_KERNEL_PAIRS, JQ_UBOOT_TRIPLETS)
- Add uboot_selected() function for pattern-based U-Boot selection
- Extract copy operations into copy_flat() and copy_recursive() helpers
- Track selected kernel pairs to filter U-Boot packages by default
Problem: armbian-base-files artifact build for Ubuntu LTS releases (jammy, noble)
fails because armbian-build looks for '{release}-updates' keys in base-files.json,
but only base release keys exist.
Root cause:
- armbian-build's apt-utils.sh uses 'jammy-updates' for LTS releases
- generate-base-files-info-json.py only adds base releases (jammy, noble)
- JSON lookup fails, artifact excluded from build matrix
Solution: Add -updates releases to the generation script
- Added 'ubuntu/jammy-updates' and 'ubuntu/noble-updates' to releases list
- Script now fetches latest security-updated versions from -updates repos
Benefits:
- Provides more recent base-files versions with security updates
- Fixes jammy/noble base-files artifact builds
- Allows jammy/noble images to build successfully
- Aligns with armbian-build's expectations
Versions:
- jammy: 12ubuntu4 -> 12ubuntu4.7 (from jammy-updates)
- noble: 13ubuntu10 -> 13ubuntu10.3 (from noble-updates)
This is the proper upstream fix. The fallback in armbian-build can remain
as a safety mechanism for when -updates keys are not available.
* Update Jira workflow to match API changes
* Update generate-jira-excerpt.yml
* Update Jira excerpt workflow for better clarity
* Drop old script, don't do it on push
* Make it the same as before
