Fix: lambda ARNs in pipeline and template.yaml to support staging and production environment

[MehulKChaudhari]

Issue Description

The Lambda ARNs used to interact with other Lambda functions for modifying concurrency limits are currently hardcoded for the production environment in the template.yaml file. This hardcoding leads to potential issues when working in different environments (e.g., staging) where different ARNs are required. This makes it difficult to manage and deploy changes across environments without manual updates to the template.

Expected Behavior

The template.yaml should dynamically select the correct Lambda ARNs based on the environment (staging or production). When in the staging environment, the template should use the staging Lambda ARNs, and when in the production environment, it should use the production Lambda ARNs. This will allow for seamless deployment and management of Lambda concurrency limits across different environments without manual intervention.

Current Behavior

Currently, the Lambda ARNs are hardcoded for the production environment in the template.yaml file. This setup does not accommodate different environments, leading to potential deployment issues and the need for manual updates to the template when working in staging or other non-production environments.

Screenshots

Reproducibility

• This issue is reproducible
• This issue is not reproducible

Additional Information

Checklist

• I have read and followed the project's code of conduct.
• I have searched for similar issues before creating this one.
• I have provided all the necessary information to understand and reproduce the issue.
• I am willing to contribute to the resolution of this issue.