dietpi-software: support dated BirdNET-Go nightly asset names

[Copilot]

BirdNET-Go nightly assets now include a date suffix (e.g. birdnet-go-linux-arm64-20260712.tar.gz), while DietPi only matched the old non-suffixed filename. This caused URL resolution for BirdNET-Go installs/updates to miss current nightly artifacts.

• Installer URL matching (dietpi/dietpi-software)

  • Relaxed BirdNET-Go release asset matching to accept both legacy and dated nightly tarball names.
  • Keeps backward compatibility with previously published nightly names.

• URL updater workflow (.github/workflows/update_urls.bash)

  • Updated BirdNET-Go aCHECK extraction regex to capture optional -YYYYMMDD suffix.
  • Updated aREGEX replacement matcher so automated URL refreshes continue to patch dietpi-software correctly.

• Release notes (CHANGELOG.txt)

  • Added a v10.6 bugfix entry documenting BirdNET-Go install failure caused by newly date-suffixed nightly archives.

# before
...-linux-$arch\.tar\.gz

# after
...-linux-$arch(?:-[0-9]{8})?\.tar\.gz

[MichaIng]

Shall we switch to stable releases? That would also assure we recognize changed URL schemes directly via CI, instead of it going through silently with an older version being downloaded. There was a release just two days ago.

Test installs: https://github.com/MichaIng/DietPi/actions/runs/29432823384

[Joulinar]

we can do this if this make sense for us.

[MichaIng]

We used nightlies since it was fast developed with many nightlies and few releases. The 2nd last release was March 2025. But maybe the 20260715 release marks a good milestone to switch for us. @mtekman what do you think: Did it settled sufficiently with the latest release, or is there still a bigger benefit for users to get nightly versions?

[mtekman]

I haven't used it much since, so can't comment on the latest release.

I'd recommend still going for the latest stable, assuming no showstopping bugs occur. I remember we only went for the nightly because of some issue with the then current release. Hopefully gone by now

[MichaIng]

I'd recommend still going for the latest stable

Yes, the latest stable in any case. So it is just about latest stable vs latest nightly. Let's assume with the recent release and version scheme change, stable releases will happen more regularly now, so we switch to use those. If it takes again very long with lots of nightlies containing valuable changes, we can revert to install nightlies. Or we add a dialogue/option to choose.