Feat: Update sha1 check to something more secure without collision

Hey aptible Team,

would it be possible on the release-notes where we can copy paste the sha hashes and the ENV+Links to add something else then sha1?

According to a lot of videos and article google already did make a collision happen where 2 files have the same hash, in 2017.

IIRC the recommendation was to use sha2-family (sha256) or sha3-family, even the Department of Defense reacted to it back in the day.

Sources:
- https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html
- https://www.youtube.com/watch?v=k0oG_jt6l7Q

No files or tests are named. Start by locating how release notes produce the copyable hashes and where the ENV and links are assembled; determine which SHA-2 or SHA-3 option the project can support. Done means release notes no longer publish SHA-1 hashes and the resulting hashes can be copied and checked reliably.

Written by the indexing model from the issue text.