program: update solana-security-txt

[2501babe]

as i discovered doing solana-program/stake#360 mailto is a syntax error:

query-security-txt ../target/deploy/spl_stake_pool.so
Error:
   0: Invalid contact `mailto:security@anza.xyz`

Location:
   /home/hana/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/query-security-txt-1.1.2/src/main.rs:35

i was going to leave the release/commit fields alone thinking this repo had its own style but i believe the hardcoded approach is fundamentally incorrect

it is possible, albeit an easy thing to overlook, to set up the github tag string in advance of a github release. its not possible for a github tag done after a release to be right, and its impossible for a hardcoded commit string to ever be right (unless you want to play with quine stuff), because we care about what these values are as of the github tagged commit. we deploy builds based on the tagged commits so by fixing metadata separately we just end up deploying binaries with the wrong values

[joncinque]

Thanks!