support AWSTOE document testing in CodePipeline

### 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**
build a feature in CodePipeline that allows AWSTOE document testing and then integration with junit CodePipeline report groups. CodePipeline is the preferred cloud native CICD, and we want the ability to test component documents prior to deployment.

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
The problem is that there is no frictionless pathway for CICD with the AWSTOE document testing and we want a solution that uses native services. The solution would provide a pattern for repository structure and would also give guidance on how to setup an AWSTOE EC2 for RHEL and Windows.

**Are you currently working around this issue?**
How are you currently solving this problem?
We are not, we wait for ImageBuilder to fail.

**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.)

Start by reviewing the requested AWSTOE document-testing flow in CodePipeline and how JUnit CodePipeline report groups could consume its results. The issue also calls for a repository structure and setup guidance for AWSTOE EC2 instances on RHEL and Windows; done means a native testing and reporting pathway with that guidance.

Written by the indexing model from the issue text.