feat: Github action for deploying to production on new release

[askayastha22]

Runbook

1. Change the version in package.json
2. Create a new release, tagging a new version (e.g. v1.0.0)
3. Let the Github action finish the deployment to app's production workspace
4. Test the new deployment from your Franklin website (e.g. https://main--wknd--hlxsites.hlx.page/)

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[askayastha22]

@ddragosd Do you have admin access to add this Github secret {{secrets.AIO_RUNTIME_AUTH_PROD}} to the action?