Add additional abilities for Manage to authenticate to a cloud object storage for doclinks

We are deploying MAS in the Oracle Cloud Infrastructure (OCI). Within OCI you are only able to select ONE designated compartment for the current supported 'Amazon S3 compatibility API'. In our environment this is set to the root compartment which is bringing a lot of additional limitations in the way we can deploy this. We would like to have additional abilities to authenticate to OCI object storage instead of S3 compatible object storage (for example using public key and private key).

Background:
We need more flexibility in where we can place all the Cloud Object Storages used by Maximo. Due to the limitations in how the MAS Manage doclinks authentication works (S3 using customer access key + secret) we are tied to this root compartment. This would result in separating resources in the root compartment on a resource-level with different user accounts for access. In relation to Terraform this would result in a lot of code to separate this access. A small misconfiguration can result in a security risk because all S3 compatible object storage will be hosted inside this compartment. You can't set this permission with the IAM policies. Even worse, our root compartment is in a different zone within the Oracle Cloud (Amsterdam) as opposed to Frankfurt zone where we are deploying MAS. From MAS application perspective it would mean that some of the application(s) data is in a different compartment, only to make it work with S3 compatible object storage.