[FEATURE REQUEST] Add Support for Adding cloud credential from polaris cli.

### Is your feature request related to a problem? Please describe.

Currently, the Polaris CLI allows users to pass a role ARN to the Polaris server when creating a catalog. However, cloud credentials (such as AWS access keys) must be provided separately via environment variables when setting up the Docker container.

Would it be possible to enhance the Polaris server API to allow client to specify both the role ARN and cloud credentials directly from a single interface? This would significantly improve usability and provide a more seamless setup experience.

Additionally, this enhancement would make Polaris more flexible and scalable for managing multiple catalogs that point to different cloud blob storage locations, especially in multi-tenant or hybrid environments.

### Describe the solution you'd like

./polaris \
--client-id ${CLIENT_ID} \
--client-secret ${CLIENT_SECRET} \
catalogs \
create \
--storage-type s3 \
--default-base-location ${DEFAULT_BASE_LOCATION} \
--role-arn ${ROLE_ARN} \
--aws_access_key_id ${AWS_ACCESS_KEY_ID}
--aws_secret_access_key: ${AWS_SECRET_ACCESS_KEY}
quickstart_catalog

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

Start by tracing the Polaris CLI `catalogs create` entry point and the corresponding server catalog API; no specific files or tests are named in the issue. Define how role ARNs and AWS credentials should be accepted and secured, then verify that a catalog can be created against its requested S3 location without relying on container environment variables.

Written by the indexing model from the issue text.