[BUG] redisenterprise: forceLinkToReplicationGroup and forceUnlink cannot link more than two databases

### API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/redisenterprise/resource-manager/Microsoft.Cache/RedisEnterprise/stable/2025-07-01/redisenterprise.json

### API Spec version

2025-07-01

### Describe the bug

POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Cache/redisEnterprise/{clusterName}/databases/{databaseName}/forceLinkToReplicationGroup?api-version=2025-07-01 unable to link more than two databases.

Workaround: databases have to be linked one at a time.

Problem also exists for forceUnlink API

This issue created as an external tracker for internal work item: https://msazure.visualstudio.com/RedisCache/_workitems/edit/36267535

### Expected behavior

Either allow more than two databases to be linked, or document & validate this behavior properly in the docs.

### Actual behavior

Linking continues for 30min and then finished in failed / unlinked state.

### Reproduction Steps

1. Create cluster A + db A
2. Create cluster B + db B
3. Create cluster C + db C
4. POST A/forceLinkToReplicationGroup with payload [B, C]

### Environment

_No response_

Start with specification/redisenterprise/resource-manager/Microsoft.Cache/RedisEnterprise/stable/2025-07-01/redisenterprise.json and inspect the forceLinkToReplicationGroup and forceUnlink operations. Reproduce the multi-database request described in the issue, then determine whether the specification should support more than two databases or document and validate the limit; done means the behavior is correctly represented and the relevant validation or documentation is covered.

Written by the indexing model from the issue text.