Expose .NET License Compliance limitations in the documentation
Problem to solve
.Net support for License Compliance doesn't cover some setups as explained in #198516 (comment 375874902).
Add a proper section to license compliance documentation with known unsupported environments, and link to either a generic feedback issue or specific one if any.
For instance, the Dependency Scanning documentation as a extra table showing unsupported languages/package managers, and linking to dedicated implementation issues.
When we don't have a specific issue for a given unsupported language, we might create a generic Feedback issue like
Add support for WHATEVER_LANGUAGE to License Compliance.