[Bug]: DocDB Cluster is missing dbSubnetGroupNameSelector

[excalq]

Is there an existing issue for this?

• I have searched the existing issues

Affected Resource(s)

• docdb.aws.upbound.io/v1beta1 - Cluster

Resource MRs required to reproduce the bug

Issue happens in compositions, which create SubnetGroups, to avoid the DocDB cluster using the unwanted "default" VPC, as happens if the Cluster's SubnetGroup is set implicitly.

Steps to Reproduce

1. Create a composition building a DocDB database, using provider-aws-family
2. Within the composition, create a SubnetGroup, a Cluster, and other resources such as a ClusterInstance, SecurityGroup, etc.

What happened?

• The SubnetGroup will be named from the XR, with a suffix. Setting metadata.name seems to be ignored.
• The Cluster has a dbSubnetGroupName parameter, but there's no way to use this with a static name due to the suffix. I suppose using status may help, but this is cumbersome to test.

Note that Cluster has a dbClusterParameterGroupNameSelector but lacks a dbSubnetGroupNameSelector. The legacy provider-aws DBCluster does have such a property. Upbound Marketplace Link

Relevant Error Output Snippet

message: 'cannot compose resources: cannot apply composed resource "db-cluster":
        failed to create typed patch object
        (/foobar--document-db-86z4d-kmnnl; docdb.aws.upbound.io/v1beta1,
        Kind=Cluster): .spec.forProvider.dbSubnetGroupNameSelector: field not
        declared in schema'

### Crossplane Version

1.15

### Provider Version

1.13.0

### Kubernetes Version

1.30

### Kubernetes Distribution

EKS

### Additional Info

_No response_