feat: Add Azure Managed Redis CRD types

[stekik]

Part of #1834 | Design: #1845

Adds the three new CRDs for Azure Managed Redis support:

• AzureManagedRedisInstance (SKR) - NoCluster mode
• AzureManagedRedisCluster (SKR) -OSSCluster mode
• AzureManagedRedis (KCP) — new provider-specific CRD, does not extend RedisInstance

Includes generated deepcopy, CRD YAMLs, RBAC roles, and azureManagedRedis feature flag.

[hyperspace-insights]

Control Panel

Hi, I'm an AI-powered Review Bot that helps you with summarizing and reviewing pull requests.
To interact with me, just use the following actions:

• 📝 Summarize PR
• 🔍 Review
• 🗑️ Delete all bot comments and reviews

[dushanpantic]

In my opinion, the API design needs to go back to the drawing board.

The offered clustering policies and SKUs no longer map to what we have used in our previous Redis offerings.
The closes thing is NoCluster for instance, and OSSCluster for cluster.

Also, we are unable to set shards/replicas manually (beside 1 via High availability), and they are now part of the selected Azure SKU.

Perhaps offering a separate instance vs cluster resource no longer makes sense.

[stekik]

Design decisions made in this PR:

1. Keeping two SKR CRDs (AzureManagedRedisInstance / AzureManagedRedisCluster)

This follows the established project convention - every other provider (AWS, GCP, Azure
legacy) splits instance and cluster into separate CRDs.

2. sku renamed to redisTier

Renamed to match the project-wide convention used by all other Redis CRDs (AwsRedisTier,
GcpRedisTier, AzureRedisTier).

3. Full redisTier enum sourced directly from armredisenterprise/v3 SDK