new: Add module for CodePipeline EKS action.

[deveshmulmule]

What this PR does / why we need it:

This change introduces a new module that demonstrates usage of CodePipeline EKS action integration.

Which issue(s) this PR fixes:

The new module demonstrates how users can construct their CD pipeline, how to setup contents of pipeline's source and how to structure of build/deploy actions.

Fixes #1411

Quality checks

• [X] My content adheres to the style guidelines
• [X] I ran make test module="<module>" it was successful (see https://github.com/aws-samples/eks-workshop-v2/blob/main/docs/automated_tests.md)
• [x] The PR has meaningful title and description of the changes that will be included in the workshop release notes

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

[netlify[bot]]

✅ Deploy Preview for eks-workshop ready!

Name	Link
🔨 Latest commit	795c35148f1b4a69ba68e7656510072b57b04a00
🔍 Latest deploy log	https://app.netlify.com/projects/eks-workshop/deploys/6864421f54b8170008ed9750
😎 Deploy Preview	https://deploy-preview-1412--eks-workshop.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[deveshmulmule]

Thanks for the review.

1. I think we need to split this across multiple pages, its a lot on one page

• One possible way of splitting is separating pipeline setup and pipeline run (initial run and subsequent run after making a code change) . Let me know your thoughts.

2. I'm planning for us to move the other automation labs to use the newer helm charts instead of kubectl manifests since its going to be cleaner than copying a bunch of stuff around. Here is the UI helm chart https://gallery.ecr.aws/aws-containers/retail-store-sample-ui-chart

• Okay. CodePipeline action does not support remote charts though. So the charts need to be in the source control. In any way, we need to setup the source of the application in pipeline - we can do this step in prepare-environment script. Let me know if that works.