[BUG] Custom Envoy image does not startup in mTLS example

[Praveen Nerellapalli]

Important note on security disclosures: If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions here or email AWS security directly.

Describe the bug
The mTLS example in the repo below is throwing an error "/bin/entryPoint.sh: line 24: /usr/bin/envoy-wrapper: No such file or directory" when the custom Envoy image starts up.
https://github.com/aws/aws-app-mesh-examples/tree/main/walkthroughs/howto-mutual-tls-file-provided-by-acm

Envoy image version: v1.21.1.2-prod

Platform
ECS

To Reproduce
Steps to reproduce the behavior:

1. Run through the example
2. Step 5 - ./infrastructure/ecs-srvice.sh will result in error
3. Error message can be found in envoy proxy logs in CloudWatch

Expected behavior
The envoy proxy should startup successfully