[azure][lfo] Enable expansion of log forwarding scopes

[agulen]

Overview

AZINTS-3876

Currently, if a user sets up log forwarding through the new onboarding experience, they are stuck with whatever LFO settings they used on the initial setup. We need to enable users to edit their existing LFO configs. This enables users to update which subscriptions have log forwarding setup and the ability to update their tag filters & PII filtering rules post-deployment.

This PR accomplishes this through few different behaviors:

• Enforcing a single LFO per Azure tenant - if multiple are found, the user is directed to uninstall extraneous ones
• If a single LFO is found, we validate that the control plane parameters are the same as the new one being configured
• There is an explicit code flow for creating a new LFO vs updating an existing one
• Refactored shared code between the create and edit flows

Misc

• Moved logging out of main and into its own file
• Introduced a flag to skip the LFO singleton check for our own dev-testing - this will not be printed in usage seen by the user

Testing

• Unit tests passing
• Manual tests look good - you can see log count dropping after I updated the LFO to have different tag filters

[datadog-official]

⚠️ Code Quality    ✅ Code Vulnerabilities    ✅ Library Vulnerabilities

⚠️ Warnings

🛠️ 1 Code quality issue detected

Low: python-best-practices/comment-fixme-todo-ownership

TODO and FIXME comments must have ownership View rule
azure/logging_install/src/azure_logging_install/validation.py:59

ℹ️ Info

🛡️ No new code vulnerabilities
📚 No new vulnerable libraries detected

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: f06efdc | Docs | Was this helpful? Give us feedback!}

[gpalmz]

LGTM