chore(ci): add temporary pipeline for v3

[leandrodamascena]

Issue number: #4826

Summary

Changes

After having developed and tested the v3 pipeline changes in a fork and personal AWS Account, we want to test the changes by running the pipeline against the BETA stage and without risking deploying to PROD.

Current state of the pipeline

The current version of the workflow has the following steps:

1. Build the package, run checks, seal it, etc.
2. Publish to PyPi using either full release version (i.e. 3.0.0) or nightly version (3.0.0.a1)
3. Publish the Lambda Layers to the BETA stage
4. Publish the Lambda Layers to the PROD stage
5. Publish the Lambda Layers to the SAR BETA stage
6. Publish the Lambda Layers to the SAR PROD stage
7. Update docs, etc.

Proposed temporary state of the pipeline

To remove the risk of mistakes and inadvertently publish to the PROD stage, we are proposing to remove/comment out all the steps in the workflow that target any PROD stage, and leave only the ones for the BETA stage.

The resulting workflow would look like this:

1. Build the package, run checks, seal it, etc.
2. Publish to PyPi using dev version (i.e. 3.0.0.dev1)
3. Publish the Lambda Layers to BETA stage
4. Publish the Lambda Layers to the SAR BETA stage

Rolling back to desired state to production

I added a comment # UNCOMMENT on all the jobs that we need to uncomment to revert when we go to production.

The ./layer_v3 folder already exists in v3 branch and we don't need to push this to develop.

User experience

Please share what the user experience looks like before and after this change

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[github-actions]

⚠️Large PR detected⚠️

Please consider breaking into smaller PRs to avoid significant review delays. Ignore if this PR has naturally grown to this size after reviews.

[github-actions]

⚠️Large PR detected⚠️

Please consider breaking into smaller PRs to avoid significant review delays. Ignore if this PR has naturally grown to this size after reviews.

[github-actions]

⚠️Large PR detected⚠️

Please consider breaking into smaller PRs to avoid significant review delays. Ignore if this PR has naturally grown to this size after reviews.

[dreamorosi]

Note that we have removed SAR from the pipeline for the time being because it needs more attention.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sthulb]

Approved but hard to verify without diffing from v2's release actions