Create a GH Action that can release a "latest" build of core to Lens QE and Lens Production

## Description

When core is "good to go", it should be able to release itself like the other open source repos.

1. Research how to properly rotate out security certificates/keys
2. With a GH action, push using `npx @adobe/reactor-packager` & `npx @adobe/reactor-releaser` to send upwards
3. Release to QE automatically on a `master` build?
4. Release to Prod on tagged version release.
5. Decide when/how to update availability to "production".

Start by investigating secure certificate and key rotation, then trace how a GitHub Action can invoke npx @adobe/reactor-packager and npx @adobe/reactor-releaser. Define the master-build path for automatic QE releases, the tagged-version path for Production, and the point at which availability changes to "production"; done means these flows and security handling are decided and automated.

Written by the indexing model from the issue text.