[BUG] Schema Definitions doesn't recursively define types

[MbolotSuse]

Rancher Server Setup

• Rancher version: v2.9-head (0b9e86cf33297eb458b3a9ac7e8a53972c0062e9)
• Installation option (Docker install/Helm Chart): Docker install
• Proxy/Cert Details: N/A

Information about the Cluster

• Kubernetes version: v1.28.6+k3s2
• Cluster Type (Local/Downstream): Local
  • If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): N/A

User Information

• What is the role of the user logged in? (Admin)
  • If custom, define the set of permissions: N/A

Describe the bug
SchemaDefinitions use a type and a subType field when defining types. In the cases where type is a map or array, the subType provides the type of the entries in the collection (for a map, the key is always a string). However, if this subType is also a map or array, there's no way to provide more information about the sub-type of that nested value.

To Reproduce

1. Run rancher/rancher:v2.9-head.
2. Get the schemaDefinition for selfsubjectreview by going to /v1/schemaDefinitions/authentication.k8s.io.selfsubjectreview.
3. Find the io.k8s.api.authentication.v1.UserInfo entry in the definitions.
4. Locate the extra resourceField. Note that type is map and subtype is array.

Result
Note that for the extra resourceField the type is map and subtype is array.

Expected Result
Type should be map[array[string]], like in /v1/schemas/io.k8s.api.authorization.v1.SubjectAccessReviewSpec for 2.8.3.

Screenshots
N/A

Additional context
N/A