New analyzer version to remove namespace analyzer

[maririos]

The release pipelines have logic to block a release if the package name is not approved. At this point, .NET is the only repo that is doing an extra check so I am cleaning the process.

PR in tools repo: Azure/azure-sdk-tools#8164

Tracking issue: Azure/azure-sdk-tools#8105

[annelo-msft]

Why remove this check instead of providing an "allow list" of namespaces differently? How are we validating in our pipelines that non-approved namespaces won't be shipped?

[jsquire]

Why remove this check instead of providing an "allow list" of namespaces differently? How are we validating in our pipelines that non-approved namespaces won't be shipped?

This was the result of an email discussion with the architects agreeing that this is no longer necessary due to API View being the authoritative voice for approved namespaces and package names. The analyzer has been a consistent point of feedback from partners who found it causing friction while onboarding to .NET.

[maririos]

Why remove this check instead of providing an "allow list" of namespaces differently? How are we validating in our pipelines that non-approved namespaces won't be shipped?

The release pipelines have logic to block a release if the package name is not approved. At this point, .NET is the only repo that is doing an extra check so I am cleaning the process. I will add you to the email thread where the discussion happened

[weshaggard]

We can probably also clean-up all the existing references to this code https://github.com/search?q=repo%3AAzure%2Fazure-sdk-for-net%20AZC0001&type=code

[azure-sdk]

API change check

API changes are not detected in this pull request.

[maririos]

/check-enforcer override