Create GH Action to Publish Project Automatically

[elliot-huffman]

Overview

This PR is to automation to publish the project from the cloud environment automatically.

Other enhancements such as publish step extraction will be recommended with future issues/PRs.

Important (Admin Steps)

The following steps are required by a repo and NPM admin to complete this PRs integration:

1. Create a new GitHub Environment called NPM.
2. Create a new NPM Granular Access Token scoped to the typescript-json and typia packages (a long-lived token would reduce the need to cycle it constantly) with read and write permissions.
3. Copy your new NPM publish token to the NPM environment as a secret named NPM_PUBLISH.
4. Profit!

Security Best Practices

• Ensure that you enable trusted approvers in your GitHub environment. This allows you to reduce the risk of a threat actor making a malicious PR designed to steal your token without trusted person approval.
• Ensure that the GH Environment is only approved to run from the master branch for any (*) tag. This prevents forks/branches from running the deploy command and only approved code can even attempt to request access.
• Scope the permissions of your granular NPM token to only the two packages typescript-json and typia, don't grant it any additional permissions.
• Do NOT store the NPM token ANYWHERE else. This could cause a complete breach of your packages. This token is privileged. GH Secrets are one way and won't allow people with repo admin access to read them out of the settings. The only things that can read secrets are GH Actions and as long as you keep an eye on the GH Actions that are being submitted to the project, you should be good.

[samchon]

Thanks for contribution.