Use azpysdk ApiStub in CI

[JennyPng]

#42601

• When using uv venv, it errored with "module pip not found", so I believe apistubgen uses pip
• To address ^, i added an ensurepip call during venv creation if using uv
• was also seeing some import error with two core packages so I switched to run the apistub command from the staging directory instead of package_dir, which resolved it 🐱

pipelines:

• core: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5688881&view=logs&j=4259cd7e-6a4b-5ca5-581a-0ae020cd9d20&t=425fe497-0bba-57e5-9867-ebf1b63abedf
• core nightly: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5688998&view=logs&j=4259cd7e-6a4b-5ca5-581a-0ae020cd9d20&t=425fe497-0bba-57e5-9867-ebf1b63abedf
• storage: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5689386&view=logs&j=21a2c31f-2cfc-5469-7d97-c1faff32ba81&t=fbdafa67-6073-5f5e-614b-f20018dbc836&s=b49e7e65-b64b-557c-018e-3fd79c15ded6
• storage nightly: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5734187&view=logs&j=4259cd7e-6a4b-5ca5-581a-0ae020cd9d20&t=425fe497-0bba-57e5-9867-ebf1b63abedf

Redoing pipelines after editing pip install

• core
• core nightly
• storage
• storage nightly

[Copilot]

Pull request overview

This pull request updates the ApiStub generation process in CI to use the new azpysdk tooling instead of the older tox-based approach. The changes address issues with uv virtual environments that were missing pip, and resolve import errors by running apistub from the staging directory instead of the package directory.

Key changes:

• Modified get_package_wheel_path to simplify return type and remove unused output token path logic
• Changed skip_install from True to False to ensure the package is installed into the venv
• Added pip installation for uv-based virtual environments to ensure compatibility with tools that depend on pip
• Updated CI pipeline to use dispatch_checks.py instead of dispatch_tox.py and switched from --toxenv to --checks argument

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
eng/tools/azure-sdk-tools/azpysdk/apistub.py	Simplified wheel path resolution, enabled package installation, added absolute path conversions, and changed working directory for apistub execution to staging directory
eng/tools/azure-sdk-tools/azpysdk/Check.py	Added pip installation step for uv virtual environments to ensure compatibility with tools requiring pip
eng/pipelines/templates/steps/run_apistub.yml	Updated to use new dispatch_checks.py script, changed toxenv to checks argument, and added environment variables for uv configuration

[Copilot]

If pip installation fails in the uv venv, the error is logged but execution continues. This could lead to failures later when tools that depend on pip are invoked. Consider either raising the exception or at least returning early to prevent subsequent failures.

Suggested change

	logger.error(f"Failed to ensure pip in uv venv: {e}")
	logger.error(f"Failed to ensure pip in uv venv: {e}")
	raise RuntimeError("Failed to ensure pip is available in the uv virtual environment.") from e

[scbedd]

I dislike that we special case this. If we need pip for the apistubgen to work, we should add it to the set of requirements for apistubgen environment. That'll address the issue without special casing here.

I could be missing something of course 😆 , lmk.

[scbedd]

We should make the environment install any necessary packages. Is apistubgen perhaps missing a dependency on pip? Or do we just add pip to the set of requirements for the environment.