Bump version numbers for v2025.0.0-alpha.0

[ethanjli]

To test this PR, either download (from the GitHub Actions job artifacts) and flash the appropriate SD card image or run the following command on a fresh installation of Raspberry Pi OS bullseye (replacing planktoscopehat with adafruithat if installing on an Adafruit HAT-based PlanktoScope):

wget -O - https://install.planktoscope.community/distro.sh | \
  sh -s -- -y -v release/v2025.0.0-alpha.0 -H planktoscopehat

Or, for a more reproducible but less convenient command which will work the same even if/when the install script is updated in the future, run (assuming the branch for this PR still exists or has been restored):

wget -O - https://raw.githubusercontent.com/PlanktoScope/install.planktoscope.community/v2024.0.0/distro.sh | \
  sh -s -- -y -t hash -v 45796b0 -H planktoscopehat

[ethanjli]

TODO before merging: first merge #620

[ethanjli]

@sonnyp If you can make your edits to software/CHANGELOG.md in this PR branch, that'd be great! I forgot an import deprecation notice (GPS HW) when I tagged documentation/v2025.0.0-alpha.0, but if we make our edits here then our changes will at least be included the git-tagged version of the changelog which we link to from the GitHub Release notes (at the top of the Notable changes since v2024.0.0 section).

[sonnyp]

I forgot an import deprecation notice (GPS HW) when I tagged documentation/v2025.0.0-alpha.0

Rewriting a doc / prerelease tag is fine by me if you want.

If you can make your edits to software/CHANGELOG.md in this PR branch,

Done in 1bb0524 - feel free to edit as you see fit.

---

I found the exercise difficult. It feels like repeating what's in the git history but without context and details.
For some changes I feel like they are too small to belong in a changelog for others I just want to put them in release notes.

Could we stop updating the software changelog after 2025 and focus on

• git history for developers
• release notes for end users

[ethanjli]

Sure! The changelog has been my imperfect 0th draft of the release notes which I draft as I merge PRs (so that then I don't have to go back over the git history when drafting release notes), but the release process after v2025.0.0 is up to you since you'll be taking over the release process. For example, maybe it'd make more sense to just keep updating a draft release notes document as you go (which is something I tried initially, and which worked okay for me), or to just write them at the end by going through the git history

[ethanjli]

I've confirmed that the adafruithat SD card image boots without any obvious problems, so I'm merging this PR now.