Add support "Identity Mapping Name" parameter

[chongwang87]

As per OIDC Token Exchange documentation, the payload support identity_mapping_name. It will be useful if we are able to define the identity mapping for different scenario (public, private repo) for single OIDC integration provider setup.

  providerConfig:
    - name: public-repo
      artifactoryUrl: <artifactoryUrl>
      matchImages:
        - "public-docker.<artifactoryUrl>"
      azure:
        . . .
        jfrog_oidc_provider_name: "azure-oidc-team-a"
        jfrog_oidc_identity_mapping_name: "sa-public-readonly"
    - name: private-repo
      artifactoryUrl: <artifactoryUrl>
      matchImages:
        - "team-a-docker.<artifactoryUrl>"
      azure:
        . . .
        jfrog_oidc_provider_name: "azure-oidc-team-a"
        jfrog_oidc_identity_mapping_name: "sa-private-team-a"

[RobinDuhan]

I don't know if this is a good idea. Because then you have to add identity mapping in the provider plugin as welll. And if you change it in Artifactory, you will have to re-deploy the provider plugin.

[chongwang87]

@RobinDuhan
For our usecase, because our enterprise managed thousand of projects. And due to compliance and security concern, each project artefacts will be segregated. Hence we have the standard structure how we manage the artifactory resource permissions (eg. public, private, etc). It will be one time setup only for us as long as we are following our standard structure during initial provisioning.