feat: sf-640 revamp cicd workflow

stanleyyconsensys commented 1 month ago

This PR is to clean up the CICD and try to standardise with metamask workflow if possible

add get starknet deployment flow
remove story book workflow, as we dont have any use case for now
combine deploy-dev, publish-npm-dev into deploy.yml, to let github taking care the dynamic variable "AWS_S3_URL" and "AWS_CLOUDFRONT_DISTRIBUTIONS_ID", and simplify the workflow
standardise package.json cmd, to have start, build, test, lint, lint, clean, serve on every workspace
remove yarn setup, as it is duplicate with yarn install, instead replace by allow-scripts from root
remove e2e, as it is not enable for now

New workflow: Main (trigger by any push or pull request to main, to test workflow and the code)

Deploy (trigger by manual, allow deploy to dev,staging,prod)

Existing workflow: lint-pr-title, terraform, release-please will remain the same

Removed workflow: e2e-tests -> removed with no use case e2e-tests-slack-notification -> removed with no use case storybook -> removed with no use case deploy-dev -> merged to deploy publish-npm-dev -> merged to deploy build-test -> merged to main

Note: In MM workflow, they dont have dev , staging deployment, but mostly 1 go to PROD by manual create a release PR request, and merge the PR, and then the pipeline will deploy to prod in Starknet workflow, we do it by auto create release PR when ever a push to main, and manual deploy to different env for more flexible choice, e.g we can deploy a version b4 release PR or after release PR

Ticket: https://consensyssoftware.atlassian.net/jira/software/projects/SF/boards/472?selectedIssue=SF-640