Support custom SSL certificate bundles

**Describe the feature you'd like**
Support custom SSL verification control in SageMaker Python SDK.

`Boto3` supports the [verify](https://boto3.amazonaws.com/v1/documentation/api/latest/reference/core/session.html#boto3.session.Session.client) parameter when creating a client, which allows either disabling SSL verification or setting a custom certificate bundle. Alternatively, a custom certificate bundle can be set through the `config` file or by the `AWS_CA_BUNDLE` environment variable.

However, these are not exposed or respected by the SageMaker Python SDK. This prevents SageMaker code from being used behind some corporate firewalls.

The lack of this feature has been noted in https://github.com/aws/sagemaker-python-sdk/discussions/3656

**How would this feature be used? Please describe.**
Corporate firewalls may re-encrypt an SSL connection with their own certificate. Unless this certificate is configured as a root certificate, SSL verification fails. This change will allow use of the SageMaker Python SDK behind such MITM-based firewalls.

**Describe alternatives you've considered**
N/A

**Additional context**
The specific error raised by SageMaker:
```
SSLError: SSL validation failed for https://sts.us-west-2.amazonaws.com/ [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1147)
```

Start by locating how the SDK creates Boto3 clients and how session or config settings are passed through. Compare those entry points with Boto3's verify parameter and AWS_CA_BUNDLE behavior. Done means callers can control SSL verification or use a custom certificate bundle, with tests covering the supported configuration paths.

Written by the indexing model from the issue text.