CodeCatalyst integrations

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Add AWSTOE EC2 instance integration with VSCode DevEnvironments with AWS CodeCatalyst. Needs ability for BOY EC2 in private subnets with AWSTOE pre-installed for windows and rhel (enterprise)

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

**Are you currently working around this issue?**
How are you currently solving this problem?

**Additional context**
Anything else we should know?

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

No repository files, tests, or entry points are named. Start by clarifying the required AWSTOE and CodeCatalyst integration behavior, including private-subnet EC2 instances and Windows and RHEL support. Done should be defined as an agreed implementation scope and validation plan for VSCode Dev Environments.

Written by the indexing model from the issue text.