feat: add getPackageAvailableVersions to public API and bump API to 1.1.0

[Eduardo Villalpando Mello (edvilme)]

Summary

• add PythonPackageGetterApi.getPackageAvailableVersions to the public API so consumers can query a package's available versions
• bump @vscode/python-environments from 1.0.0 to 1.1.0
• synchronize both API lockfile version fields
• document the public API changes since the latest npm release

API changes

• add PythonPackageGetterApi.getPackageAvailableVersions(environment, packageName): Promise<Pep440Version[] | undefined> — exposes a package's available versions (newest-first) to API consumers, delegating to the environment's package manager and resolving to undefined when version listing is unsupported
• re-export Pep440Version for package manager version APIs
• add PackageInfo.isTransitive and GetPackagesOptions.skipCache
• add optional package manager hooks for watch targets, direct dependencies, tool versions, available package versions, and install-spec formatting
• add the optional GetPackagesOptions parameter to PackageManager.getPackages and PythonPackageGetterApi.getPackages
• update PackageManager.refresh and PythonPackageGetterApi.refreshPackages to return the refreshed package list when available

Validation

• npm run lint
• npm run compile-tests
• npm run unittest (1494 passing, 5 pending)
• git diff --check

[Eduardo Villalpando Mello (edvilme)]

Adding "skip tests" label since this functionality already exists but is now being exposed to the public API

[Eleanor Boyd (eleanorjboyd)]

see two items about refresh and the exported top level items

[Stella Huang (StellaHuang95)]

🔒 Automated review in progress — Stella Huang (@StellaHuang95) is auto-reviewing this PR.

[Stella Huang (StellaHuang95)]

Approved via Review Center.

[Eleanor Boyd (eleanorjboyd)]

Thanks for addressing the previous feedback. The packed-package validation still has three blocking holes:

1. The publish pipeline runs cp ../src/api.ts src/main.ts, but api/src is ignored and absent from a clean checkout. The step fails before compilation unless it creates the directory first.

2. api/test/consumer.ts does not enforce the exact public return type. Assigning an explicitly narrow implementation to PythonPackageGetterApi["getPackageAvailableVersions"] still compiles if the published contract is widened to Promise<unknown> or Promise<any>. Please assert exact type equality or call the typed API and assign its result to Promise<Pep440Version[] | undefined>.

3. The package test exercises conditional exports; require.resolve() does not prove that top-level main is present, and import.meta.resolve() can resolve a missing target. Please inspect the installed package metadata and assert top-level main and types plus all referenced target files exist.

Also, normalize or realpath the expected and resolved temporary paths: on macOS Node may return /private/var/... for a test root created as /var/..., causing a false failure.