build: initial CRT support

[DanStough]

Description

Adds CRT support for consul-aws based on the same setup used in consul-dataplane. It still requires some setup on the rel-eng side, which is in process.

I will also assign someone in rel-eng to review once they are assigned to the help desk ticket.

Notes

Since CRT handles most of the build and release process, I gutted the Makefile and associated build scripts.

Example version output:

> consul-aws version
consul-aws 0.1.3-dev
Git Commit: 72245af+CHANGES

Required for this PR

• HASHIBOT_PRODSEC_GITHUB_TOKEN (Used for the security scanner)

Future PRs

• More actions for testing.
• Documentation for running the integration tests.

[zalimeni]

ELEVATED_GITHUB_TOKEN (Used for the security scanner)

Minor: If security scans are the only reason we need this, we can ask for @dduzgun-security 's help provisioning a tighter-scoped token like we did in consul

[zalimeni]

Some minor comments, but overall this looks great to me. Thank you for all the work on this and attention to detail porting over existing patterns 🙏🏻

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.