Use Domain ID instead of path while resolving User

[vignesh-goutham]

Issue #, if available: Does not fix but alleviates #321 in few code paths.

Description of changes:
The ListUsers API only returns a domain ID and a domain name pertaining to the user provided as input. Using domain name in place of domain path, leads to assuming the parent domain here is ROOT. Instead this change, sets the domain id which is more deterministic and leads to clear identification and resolution of domain.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-cloudstack ready!

Name	Link
🔨 Latest commit	16117cc
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-cluster-api-cloudstack/deploys/65416ee7c803790008053c97
😎 Deploy Preview	https://deploy-preview-322--kubernetes-sigs-cluster-api-cloudstack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[k8s-ci-robot]

Hi @vignesh-goutham. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[g-gaston]

lgtm
/ok-to-test

Is this difficult to test through unit tests?

[rohityadavcloud]

/approve

[vignesh-goutham]

lgtm /ok-to-test

Is this difficult to test through unit tests?

Yea, unit test for the changes in this PR doesnt provide us much. But for the proper change to fix domain resolution using names, we can expect unit tests to capture and test different domains with different leveled paths.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrisdoherty4, rohityadavcloud, vignesh-goutham

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:

• OWNERS [chrisdoherty4,rohityadavcloud]

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

[chrisdoherty4]

/lgtm

[g-gaston]

/cherry-pick release-0.4

[vignesh-goutham]

/cherrypick release-0.4