feat(layer): publish SAR v2 via Github actions

[rubenfonseca]

Issue number: #1543

Summary

This PR adds support for creating the v2 SAR via Github Actions.

Changes

Please provide a summary of what's being changed

• Rename V2 Layer and Canary stacks to LayerV2Stack and CanaryV2Stack, to avoid clashing with the existing v1 stack which we will want to maintain
• Re-use the Lambda Layer artifact to publish the SAR using SAM
• No more dependencies with internal pipelines
• Authentication using OIDC as a jump role

User experience

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

A successful SAR release will now look like this (please ignore the Layer deployment failure):

Checklist

• After merge, remove feat/sar-v2 from environment branches

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.

[heitorlessa]

Looks great! It gives me a great relief to have the entire release now centralized.

Changes:

• GH is deprecating set-output (no ETA yet) - suggested the superseding mechanism
• Note to create a Maintenance issue to convert the longest inline parts into a script (after V2 is launched, not now)
• Pieces where a comment could be helpful for our future selves

[rubenfonseca]

Screenshot updated