Add DV list keys on ResourceClaimStatus.Devices

[lalitc375]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR enables the use of pointer fields as keys in listType=map lists in the Kubernetes API. Currently, fields of pointer types cannot be used as keys for lists with listType=map semantics. This PR lifts that restriction by updating the code generator and validation logic to correctly handle pointer types in listMapKeys.

The key changes are:

• The validation-gen code generator is updated to handle pointer types in listMapKey by checking for nil and dereferencing pointers before comparison.
• The ResourceClaimStatus.Devices field is updated to use listType=map with a composite key that includes the shareID field, which is a pointer type.
• New test cases have been added to verify the functionality of using pointer fields in listMapKeys.

This change provides more flexibility in defining API types by allowing the use of pointer fields as keys in maps, which is useful in scenarios where a key field can be optional.

Which issue(s) this PR is related to:

N/A

Special notes for your reviewer:

NONE

Does this PR introduce a user-facing change?

NONE

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

- [KEP]: https://github.com/kubernetes/enhancements/issues/5073

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lalitc375
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• pkg/apis/OWNERS
• pkg/registry/OWNERS
• staging/src/k8s.io/api/OWNERS
• staging/src/k8s.io/code-generator/OWNERS

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

[k8s-triage-robot]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.