fix(logging): replace inline AMA resources with avm/ptn/alz/ama module

[oZakari]

Overview/Summary

Replace inline AMA resource declarations in the logging module with the br/public:avm/ptn/alz/ama:0.2.0 AVM pattern module. This fixes the duplicate lock resource name collision that causes InvalidTemplate errors when using Azure Deployment Stacks.

Related Issues/Work Items

• Fixes [Bug]: Core-Logging pipeline step fails with error "GlobalResourceLock' is not defined in the template" Azure-Landing-Zones#4110
• Related AVM fix: [AVM Module Issue]: Duplicate lock resource names cause InvalidTemplate error in Deployment Stacks bicep-registry-modules#6794

This PR fixes/adds/changes/removes

1. Removes inline resource declarations for: User Assigned Managed Identity, VM Insights DCR (PerfAndMap + PerfOnly), Change Tracking DCR, MDFC SQL DCR, and all associated lock resources (~473 lines removed)
2. Adds a single module call to br/public:avm/ptn/alz/ama:0.2.0 which deploys all AMA resources with unique lock names that prevent Deployment Stacks validation failures
3. Removes AMA-specific outputs (outUserAssignedManagedIdentity*, outDataCollectionRule*) — these are now available via the AVM module directly
4. Preserves all existing parameters for backward compatibility (unused DCR lock params suppressed with #disable-next-line)

Breaking Changes

1. Removed outputs: outUserAssignedManagedIdentityId, outUserAssignedManagedIdentityPrincipalId, outDataCollectionRuleVMInsightsName, outDataCollectionRuleVMInsightsId, outDataCollectionRuleChangeTrackingName, outDataCollectionRuleChangeTrackingId, outDataCollectionRuleMDFCSQLName, outDataCollectionRuleMDFCSQLId — no downstream consumers found in the repo

Testing Evidence

• Bicep build: bicep build completes with no errors
• Deployed successfully to rg-alz-logging-test in sub-amba-repobackup subscription using logging.parameters.min.json
• Deployment alz-logging-test-3 succeeded with state Succeeded

As part of this Pull Request I have

• Read the Contribution Guide and ensured this PR is compliant with the guide
• Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
• Checked for duplicate Pull Requests
• Associated it with relevant GitHub Issues
• (ALZ Bicep Core Team Only) Associated it with relevant ADO Items
• Ensured my code/branch is up-to-date with the latest changes in the main branch
• Performed testing and provided evidence.
• Updated one or more of the following tests (if required)
  • Unit
  • Linting
  • E2E (End-To-End)
  • ValidateAzCloud (Base validation in Azure Cloud)
  • ValidateMcCloud (Base validation in Azure China Cloud)
• Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
• If relevant, created or updated Code Tours here