OCI provider - implement Workload Identity auth - cherry pick for release 1.27

[streamnsight]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Implements Workload Identity auth method for the OCI cloud provider.
Workload Identity offers a more granular way to give permissions to access OCI resources.

Special notes for your reviewer:

The majority of file changes comes from the OCI SDK upgrade required for this update, the implementation is otherwise a minor change.

Does this PR introduce a user-facing change?

Added OCI Cloud Provider Workload Identity support
Workload Identity provides a more granular way to secure workloads that require access to OCI resources

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Workload Identity is set by the use of the environment variable `OCI_USE_WORKLOAD_IDENTITY=true`
as well as the `OCI_RESOURCE_PRINCIPAL_VERSION` (1.1 or 2.2) and `OCI_RESOURCE_PRINCIPAL_REGION` since Workload Identity is backed by the Resource Principal auth mechanism.
`OCI_USE_WORKLOAD_IDENTITY=true` takes precedence over `OCI_USE_INSTANCE_PRINCIPAL=true` if set.

Furthermore, a policy needs to be defined to allow the workload to use OCI resources as follow:

Allow any-user to manage cluster-node-pools in compartment <compartment name> where ALL {request.principal.type='workload', request.principal.namespace ='<namespace>', request.principal.service_account = 'cluster-autoscaler', request.principal.cluster_id = 'ocid1.cluster.oc1....'}
Allow any-user to manage instance-family in compartment <compartment name> where ALL {request.principal.type='workload', request.principal.namespace ='<namespace>', request.principal.service_account = 'cluster-autoscaler', request.principal.cluster_id = 'ocid1.cluster.oc1....'}
Allow any-user to use subnets in compartment <compartment name> where ALL {request.principal.type='workload', request.principal.namespace ='<namespace>', request.principal.service_account = 'cluster-autoscaler', request.principal.cluster_id = 'ocid1.cluster.oc1....'}
Allow any-user to read virtual-network-family in compartment <compartment name> where ALL {request.principal.type='workload', request.principal.namespace ='<namespace>', request.principal.service_account = 'cluster-autoscaler', request.principal.cluster_id = 'ocid1.cluster.oc1....'}
Allow any-user to use vnics in compartment <compartment name> where ALL {request.principal.type='workload', request.principal.namespace ='<namespace>', request.principal.service_account = 'cluster-autoscaler', request.principal.cluster_id = 'ocid1.cluster.oc1....'}
Allow any-user to inspect compartments in compartment <compartment name> where ALL {request.principal.type='workload', request.principal.namespace ='<namespace>', request.principal.service_account = 'cluster-autoscaler', request.principal.cluster_id = 'ocid1.cluster.oc1....'}

[streamnsight]

@jlamillan Could you review / approve?

[jlamillan]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlamillan, streamnsight

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• cluster-autoscaler/cloudprovider/oci/OWNERS [jlamillan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment