Plugin using outdated OCI library which have outdated endpoints for new regions

**Describe the bug**
A clear and concise description of what the bug is.
There is a new Regions and Realms which available only in V65 versions of https://github.com/oracle/oci-go-sdk. All examples describes that we have to use this version for module import [github.com/oracle/oci-go-sdk](https://github.com/oracle/oci-go-sdk)/v65/* but in code you have github.com/oracle/oci-go-sdk/* and version when i'm using (go get: added github.com/oracle/oci-go-sdk v24.3.0+incompatible), which is outdated. .
New regions and realms as example provided only in https://github.com/oracle/oci-go-sdk/blob/master/common/regions.go#L202

**To Reproduce**
Steps to reproduce the behavior:

Tenancy in OC9 new OCI realm
Use instruction setup auth according to site - https://www.vaultproject.io/docs/auth/oci
During auth vault send request to wrong endpoint
`Error authenticating: can not create client, bad configuration: failed to get security token: failed to renew security token: failed to get security token: failed to call: Post "https://auth.me-dcc-muscat-1.oraclecloud.com/v1/x509": dial tcp: lookup [auth.me-dcc-muscat-1.oraclecloud.com](http://auth.me-dcc-muscat-1.**oraclecloud.com**/) on 169.254.169.254:53: no such host`
but real endpoint must have **oraclecloud9.com**

**Expected behavior**
This documentation working https://www.vaultproject.io/docs/auth/oci in oc9 new realm.

**Additional context**
Its a blocker for whole Oracle Org using OCI Auth in Vault

Start by tracing the plugin's github.com/oracle/oci-go-sdk imports and compare the dependency version with the v65 SDK, especially common/regions.go. Reproduce authentication with the documented OCI setup in the OC9 realm and verify that the generated endpoint uses oraclecloud9.com rather than oraclecloud.com.

Written by the indexing model from the issue text.