fix: Troubleshoot Azure RBAC limits

[ThomVanL]

Provided fixes for:

• "Solution 2 - Remove Redundant Role Assignments" when using the conditions query. The condition column was missing in the summarize operator statement.
• The name 'AuthorizationResources' does not refer to any known table, tabular variable or function. According to the KQL entity naming rules, a table entity name is case-sensitive.

[prmerger-automator]

@ThomVanL : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit fa8f289:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/role-based-access-control/includes/query/authorization-same-principal-scope-condition.md	✅Succeeded
articles/role-based-access-control/includes/query/authorization-same-principal-scope.md	✅Succeeded
articles/role-based-access-control/includes/query/authorization-same-role-principal-condition.md	✅Succeeded
articles/role-based-access-control/includes/query/authorization-unused-custom-roles.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

@rolyon

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team