Generate list of released executables from the manifest

Context

Issue: #2606 (closed)

Manually testing the MR

# checkout this branch
$ git checkout richard-manifest-list-released-executables

# checkout scripts/ci/release.sh for modification
$ git checkout master -- scripts/ci/release.sh

# make sure to add `echo "$binaries"; exit 1` after line 11
$ vim scripts/ci/release.sh

# run the script
$ bash scripts/ci/release.sh | tr ' ' '\n' | sort
tezos-signer
tezos-codec
tezos-client
tezos-admin-client
tezos-node
tezos-tx-rollup-node-alpha
tezos-tx-rollup-client-alpha
tezos-sc-rollup-node-alpha
tezos-sc-rollup-client-alpha
tezos-accuser-alpha
tezos-baker-alpha
tezos-tx-rollup-node-014-PtKathma
tezos-tx-rollup-client-014-PtKathma
tezos-sc-rollup-node-014-PtKathma
tezos-sc-rollup-client-014-PtKathma
tezos-accuser-014-PtKathma
tezos-baker-014-PtKathma
tezos-tx-rollup-node-013-PtJakart
tezos-tx-rollup-client-013-PtJakart
tezos-sc-rollup-node-013-PtJakart
tezos-sc-rollup-client-013-PtJakart
tezos-accuser-013-PtJakart
tezos-baker-013-PtJakart
tezos-accuser-012-Psithaca
tezos-baker-012-Psithaca

# cat `binaries-for-release` and see that the result is the same as above
$ cat binaries-for-release | sort
tezos-signer
tezos-codec
tezos-client
tezos-admin-client
tezos-node
tezos-tx-rollup-node-alpha
tezos-tx-rollup-client-alpha
tezos-sc-rollup-node-alpha
tezos-sc-rollup-client-alpha
tezos-accuser-alpha
tezos-baker-alpha
tezos-tx-rollup-node-014-PtKathma
tezos-tx-rollup-client-014-PtKathma
tezos-sc-rollup-node-014-PtKathma
tezos-sc-rollup-client-014-PtKathma
tezos-accuser-014-PtKathma
tezos-baker-014-PtKathma
tezos-tx-rollup-node-013-PtJakart
tezos-tx-rollup-client-013-PtJakart
tezos-sc-rollup-node-013-PtJakart
tezos-sc-rollup-client-013-PtJakart
tezos-accuser-013-PtJakart
tezos-baker-013-PtJakart
tezos-accuser-012-Psithaca
tezos-baker-012-Psithaca

# in fact if you want to rigorously check that they are actually equal, you could pass the results through diff
$ diff -u <(bash scripts/ci/release.sh | tr ' ' '\n' | sort) <(cat binaries-for-release | sort)

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR