Bump up versions in etc/versions.json

Data in etc/versions.json should be updated just before the release.

This should probably be a part of the release process. For the first iteration, I wanted to create a dedicated issue for it.

• update the date field. Set the value to the current date when the file is being updated. Please use the yyyy-mm-dd format.
• update released software versions for Kea according to https://www.isc.org/download/#Kea
  • if needed, update the version fields for all currentStables and latestDev. These values MUST be valid semvers.
  • if needed, update the releaseDate fields for all currentStables and latestDev. Please use yyyy-mm-dd format. Please note that the exact date can be retrieved from the release notes. Stork UI, however, displays the date with monthly granularity, e.g., 2024-07-31 release date will be displayed as July 2024
  • if needed, update eolDate fields for all currentStables. Please use yyyy-mm-dd format. Stork UI displays the EoL date with monthly granularity.
  • if a security release was issued recently, add/update latestSecure release information. releaseDate and version fields are mandatory. The rules for these fields are the same as for currentStable and latestDev releases.
• update released software versions for BIND9 according to https://www.isc.org/download/#BIND
  • if needed, update the version fields for all currentStables and latestDev. These values MUST be valid semvers. Please note that one of the stable BIND9 releases is the ESV release. In the JSON file it has the ESV field set to true.
  • if needed, update the releaseDate fields for all currentStables and latestDev. Please use yyyy-mm-dd format. Please note that the exact date can be retrieved from e.g., https://lists.isc.org/pipermail/bind-announce/ mailing list. Stork UI, however, displays the date with monthly granularity, e.g., 2024-10-16 release date will be displayed as October 2024
  • if needed, update eolDate fields for all currentStables. Please use yyyy-mm-dd format. Please note that EOL dates often are given with quarter granularity. The eolDate may be set to the first day of the month following the given quarter, e.g., Q2, 2026 -> 2026-07-01. Stork UI displays the EoL date with monthly granularity.
• update released software versions for Stork
  • update the version field for the currently ongoing release (either stable, dev or security release). This MUST be a valid semver.
  • update the releaseDate field for the currently ongoing release - this is set before the actual release date, so it must be the best possible estimate. Please use yyyy-mm-dd format. Stork UI, however, displays the date with monthly granularity, e.g., 2024-07-31 release date will be displayed as July 2024
  • if needed, update eolDate fields for all currentStables. Please use yyyy-mm-dd format. Stork UI displays the EoL date with monthly granularity.
• Once the etc/versions.json file is updated, run Stork UI+server and verify that the server doesn't complain about unmarshalling the JSON, and all Versions are correctly displayed in the UI.