Update transfer table to include resource locks transfer incompatibility

[oc159]

Resource Locks are not migrated as part of the subscription transfer process - validated 16/01/25.
Include in documentation such that individuals can export and import them upon initiating their subscription transfers.

[prmerger-automator]

@oc159 : 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 c61d5c8:

💡 Validation status: suggestions

File	Status	Preview URL	Details
articles/role-based-access-control/transfer-subscription.md	💡Suggestion		Details

articles/role-based-access-control/transfer-subscription.md

• Line 90, Column 38: [Suggestion: docs-link-absolute - See documentation] Absolute link '/https://learn.microsoft.com/en-us/cli/azure/resource/lock?view=azure-cli-latest#az-resource-lock-list' will be broken in isolated environments. Replace with a relative link.
• Line 90, Column 221: [Suggestion: docs-link-absolute - See documentation] Absolute link '/https://learn.microsoft.com/en-us/cli/azure/resource/lock?view=azure-cli-latest' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

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

[v-dirichards]

@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