chore: updated script to assign AKS cluster role to user

[Rafi-Microsoft]

This pull request enhances the AKS (Azure Kubernetes Service) deployment script by ensuring that the currently signed-in user has the necessary RBAC Cluster Admin role before connecting to the cluster. This helps prevent permission issues during deployment.

AKS role assignment improvements:

• Added a check to see if the current user already has the "Azure Kubernetes Service RBAC Cluster Admin" role on the target AKS resource, and assigns it if missing. This ensures the user has appropriate permissions before connecting to the cluster.

Other changes:

• Minor formatting update at the top of the resourcedeployment.ps1 script (no functional impact).

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information

[github-actions]

🎉 This PR is included in version 1.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀