[Bug]: Ubuntu Resolute builds fail because generated base-files.json has no resolute entry

### What happened?

Armbian image builds using RELEASE=resolute and ARCH=arm64 started failing today during the armbian-base-files artifact step.

The build reaches:

artifact [ armbian-base-files :: armbian-base-files() ]

and then repeatedly fails with:

Could not find package filename for 'base-files' in distro repo
looking for base-files, found_package_filename is null

The failing function is:

apt_find_upstream_package_version_and_download_url base-files

I traced the lookup path and found that Armbian’s build framework reads the generated base-files.json and expects an entry for:

.resolute.arm64

The current generated data/base-files.json in armbian/armbian.github.io no longer contains a resolute key at all, so the lookup returns null and the build aborts after 10 retries.

I was successfully building Resolute images on 2026-09-10. The armbian.github.io data branch was rebuilt on 2026-09-11 at 11:27:25 UTC, commit:

1c45b761bf642428086ae630023862140dddc8a2

After that generated data rebuild, the resolute entry is missing.

The generator script still explicitly includes ubuntu/resolute, but it skips an entire release if package metadata retrieval fails, so it appears that Resolute was dropped from the generated JSON after a fetch/parsing failure.

This reproduces from a completely clean Armbian build checkout with no custom userpatches, and pinning an older Armbian build-framework commit still fails because it consumes the current generated base-files.json.

### How to reproduce?

1. Start from a clean Armbian build checkout.

2. Make sure no custom userpatches are present.

3. Run:

./compile.sh build \
BOARD=orangepi5pro \
BRANCH=edge \
RELEASE=resolute \
BUILD_DESKTOP=yes \
BUILD_MINIMAL=no \
DESKTOP_ENVIRONMENT=kde-plasma \
DESKTOP_TIER=full \
KERNEL_CONFIGURE=no \
COMPRESS_OUTPUTIMAGE=sha,img

4. The build proceeds through U-Boot, kernel and firmware packaging, then fails at:

artifact [ armbian-base-files :: armbian-base-files() ]

5. The failing output is:

Could not find package filename for 'base-files' in distro repo
looking for base-files, found_package_filename is null

Command failed, retrying in 15s
apt_find_upstream_package_version_and_download_url base-files

6. After 10 retries the build aborts in:

lib/functions/artifacts/artifact-armbian-base-files.sh

This reproduces on a completely clean checkout with no custom image modifications.

It also reproduces when pinning the Armbian build framework to commit:

3e173225f1285f9d1ff5bb09f596f1d011ea5fcd

because the build still consumes the current generated base-files.json, where the resolute entry is missing.

### Branch

main (main development branch)

### On which host OS are you running the build script and observing this problem?

Other

### Are you building on Windows WSL2?

- [ ] Yes, my Ubuntu/Debian/OtherOS is running on WSL2

### Relevant log URL

_No response_

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Start with lib/functions/artifacts/artifact-armbian-base-files.sh and the apt_find_upstream_package_version_and_download_url lookup, then inspect data/base-files.json in armbian/armbian.github.io and the generator mentioned in the report. Reproduce with the provided compile.sh command and verify that generated data includes a .resolute.arm64 entry and the armbian-base-files artifact completes.

Written by the indexing model from the issue text.