Manually removing the AMA extension breaks re-deployment by policy

[QBY-MauriceBaerisch]

Describe the bug
If the Azure Monitor agent extension has been installed on a resource and is being removed,
the policy recognizes the resource as non-compliant. However, the re-deployment initiated
on a remediation task fails because it believes the AMA extension is already installed.

To Reproduce
Steps to reproduce the behavior:

1. Have the AMA policy defined and assigned to a scope
2. Create a virtual machine in that scope
3. After a while, the policy should have deployed the Azure Monitor agent
4. Go to your virtual machine, navigate to extensions, and remove the agent by hand
5. Start a remediation task for the AMA policy (make sure to re-evaluate compliance)
6. After a while, the bug above should occur

Expected behavior
The re-deployment initiated on a remediation task should simply re-install the Azure Monitor extension.
(This could also be a feature request regarding use cases like: uninstall all AMA extensions and reinstall them with the proxy parameter specified in an updated assignment).

Desktop (please complete the following information):

• OS: Win11
• Browser Chrome

Additional context
Occured in my VS enterprise dev subscription.