[BUG] Enoy Proxy container fails to initialize while trying to create an app mesh using the dj-app

**Describe the bug**
Ran into an issue while trying to create an app mesh using the dj-app at aws-app-mesh-examples/examples/apps/djapp/

With the current deployment files, when the envoy proxy sidecar container is automatically injected, it will not have the necessary permission "appmesh:StreamAggregatedResources". This is because the iamserviceaccount that is created as part of the tutorial is not included in the base app deployment definition.

**Platform**
EKS

**To Reproduce**
Steps to reproduce the behavior:
1. git clone https://github.com/aws/aws-app-mesh-examples
2. cd aws-app-mesh-examples/examples/apps/djapp/
3. kubectl apply -f 1_base_application/base_app.yaml
4. Deploy appmesh-controller using helm
5. kubectl apply -f 2_meshed_application/meshed_app.yaml
6. Envoy proxy sidecar container fails to initialize due to an iam permission issue.

**Expected behavior**
The Envoy proxy sidecar container should initialize successfully and there should not be any iam permission error.

**Additional context**
After adding the serviceAccountName (which has the correct role with policies attached) to all the deployment definition in 1_base_application/base_app.yaml the envoy proxy container initialized successfully without any issue.

Start in examples/apps/djapp/1_base_application/base_app.yaml and compare it with 2_meshed_application/meshed_app.yaml, focusing on the service account used by each deployment. Reproduce the setup with the listed kubectl commands after deploying appmesh-controller with Helm. Done means the injected Envoy sidecar initializes without an IAM permission error.

Written by the indexing model from the issue text.