Split deploy canary demo script into smaller scripts

[harshitOberoi]

Issue #:
After adding deployment of ChimeSDKMeetings specific demos to Deploy Canary Demo GitHub Action which works on merging into master branch the average deployment time increased from 25 minutes to 1 hour.

Description of changes:

1. Removed deploy-canary-demo script which builds browser demo and deploys serveless demo to all the canary regions and split it into region specific scripts:
   a) build-browser-demo
   b) deploy-canary-demo-alpha
   c) deploy-canary-demo-beta
   d) deploy-canary-demo-gamma
2. Updated deploy.yml to add multiple jobs to run all the above scripts in parallel

Testing:

Can these tested using a demo application? Please provide reproducible step-by-step instructions.
No

Checklist:

1. Have you successfully run npm run build:release locally?
   Yes

2. Do you add, modify, or delete public API definitions? If yes, has that been reviewed and approved?

3. Do you change the wire protocol, e.g. the request method? If yes, has that been reviewed and approved?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[michhyun1]

I think you have the right idea - I think you want 3 jobs:

1. deploy_alpha_demo

• checkout package
• install SAM
• run alpha demo deploy script (cd into demo, npm i, npm build, set alpha aws creds, deply)

2. deploy_beta_demo

• checkout package
• install SAM
• run beta demo deploy script (cd into demo, npm i, npm build, set beta aws creds, deply)

3. deploy_gamma_demo

• checkout package
• install SAM
• run gamma demo deploy script (cd into demo, npm i, npm build, set gamma aws creds, deply)

[ltrung]

Do you commit the logout file by mistake?

[harshitOberoi]

@ltrung lockfile was added as i had to provide executable access to deploy_canary_demo script. As i removed and then added it again

[ltrung]

Is the logout.js committed by mistake?

[harshitOberoi]

@ltrung The logout.js was added as i deleted the deploy_demo_canary script and when i added it back i had to provide executable access and that added logout.js

[michhyun1]

Need to rebase and then force push again. LGTM otherwise - @ltrung @devalevenkatesh any concerns?

[ltrung]

Do you need prod canary? If so should you update the postrelease script which release prod demo app.

[harshitOberoi]

we do not need prod canaries as Gamma Canaries are testing ChimeMeetingSDK prod endpoints