Feature Request: Apply Proxy Only to CodeDeploy Endpoint, Not S3

Description:
We are currently using the AWS CodeDeploy agent in our deployment pipeline. However, we have encountered a limitation with the proxy settings. The agent only offers a single proxy setting, which is applied to all endpoints. We need to use a proxy to access the CodeDeploy endpoint but not for accessing S3. This limitation is causing issues in our deployment process.

Proposed Solution:
We propose adding a configuration option to apply the proxy setting only to the CodeDeploy endpoint and not to S3. This would allow users to configure the proxy specifically for CodeDeploy, while allowing direct access to S3, providing greater flexibility and resolving the issues we are facing.

Use Case:
Our organization uses a proxy to access the CodeDeploy endpoint for security and compliance reasons. However, accessing S3 through the same proxy introduces latency and connectivity issues. By having the ability to apply the proxy only to the CodeDeploy endpoint, we can ensure efficient and secure access to both services.

Steps to Reproduce:

1. Configure the AWS CodeDeploy agent with a proxy setting.
2. Attempt to deploy an application using CodeDeploy.
3. Observe that the proxy setting is applied to both the CodeDeploy endpoint and S3, causing issues with S3 access.

Expected Behavior:
The AWS CodeDeploy agent should allow the proxy setting to be applied only to the CodeDeploy endpoint, enabling users to configure the proxy as needed for CodeDeploy while accessing S3 directly.

Start by tracing how the CodeDeploy agent reads its proxy configuration and establishes connections to CodeDeploy and S3. Confirm the requested configuration behavior and identify the existing tests covering proxy use. Done means CodeDeploy requests use the configured proxy while S3 access can bypass it, with tests demonstrating both paths.