Rework release script

[totten]

• General concept: Split apart the official releases and the pre-releases:
  • Official releases are tagged and signed. They are built semi-manually (run a script; supply credentials during build).
  • Pre-releases are built automatically by CI.
• Official releases
  • Releases are posted to bothhttps://download.civicrm.org/cv/ and Github
  • There are four primary files for each release:
    • cv-X.Y.Z.phar (main executable)
    • cv-X.Y.Z.phar.asc (for gpg verification)
    • cv-X.Y.Z.SHA256SUMS (for sha256 verification)
    • cv-X.Y.Z.SHA256SUMS.asc (because... why not...)
  • Additionally, the latest official release is aliased as cv.phar (and cv.phar.asc et al)
• Pre-releases
  • Pre-releases are posted to https://download.civicrm.org/cv/
  • There is only one primary file (cv-EDGE-{version}.phar).
  • Additionally, the latest pre-release is aliased as cv-EDGE.phar.
• Script organization
  • ./scripts/build.sh moves into the subdir (ie ./build.sh => ./scripts/build.sh). It is used by official and pre-releases buidls.
  • ./scripts/releaser.php does the official release
  • ./scripts/tag.sh goes away. (This is folded into releaser.php.)

[totten]

Test failures are false-negatives (unrelated networking issues).