Creating a development CodePipeline project with image scanning and an EKS cluster

In the previous section, we raised a PR from feature-anothercatalog to the develop branch after fixing a security recommendation. That means the new feature is ready to get merged to the develop branch and to deploy on the development EKS cluster. Mostly, the development environment runs multiple builds and deployments in a day. These days, you will see most enterprises and start-ups roll out their features every day. In this section, we will create a CodePipeline project that will get triggered the moment the PR gets merged from feature-anothercatalog to the develop branch. We also need to make sure that the build and deployment should take place only to the microservice that has code changes. We discussed in the first section that either we can choose polyrepo and multiple pipelines or we can have a monorepo and path-based multi-pipeline. It was also highlighted that currently, we can't do path...