Enforce Conda pyproject.toml metadata in verifywhl

[JennyPng]

closes #44883

• (data plane) packages with stable releases are required to have a Conda tool section in their pyproject.toml to specify if packages are to be released individually or as part of a bundle
• existing stable packages have already been batch updated
• going forward, service teams should be responsible for specifying this information
• also adds tests (and switches tests to test azpysdk verify_whl instead of tox verify_whl)

example pipeline:

• core: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5881030&view=logs&j=b70e5e73-bbb6-5567-0939-8415943fadb9&t=d32d6c50-584d-5bc8-5a7d-7426470979cb

• storage: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5881294&view=logs&j=b70e5e73-bbb6-5567-0939-8415943fadb9&t=d32d6c50-584d-5bc8-5a7d-7426470979cb

[Copilot]

Pull request overview

This pull request enforces that Python packages with stable releases on PyPI must include a [tool.azure-sdk-conda] section in their pyproject.toml file. This automation supports the Conda release process by ensuring service teams specify whether packages should be released individually or bundled.

Changes:

• Adds validation to check for Conda metadata in packages with stable PyPI versions
• Fixes logging calls to use the correct logger instance
• Removes unused import statement

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

[JennyPng]

/check-enforcer override