Unresolvable UCRT DLL warings were previously suppressed for
Windows 10 and 11, but they also affect maching Windows Server versions.
Suppress the warnings for all 10+ versions.

…9357)

…9359)

…adata (#9345)

Account for possibility of an Anaconda package not providing a `depends`
entry in its distribution metadata. Fixes error during initialization
of the `conda` hook utility module in Anaconda environments where such
packages (e.g., `tzdata`) happen to be installed.

…rser

Have the command-line parser in `test_spec_options` explicitly
specify the program name, to ensure it always matches what the
test expects to find in the output  (i.e., 'pyi_spec_options.spec').

Starting with python 3.14, the automatically-inferred program name
becomes `python -m pytest` when `pytest` is launched as a module,
which ends up breaking the test.

Relax the installer-type check that gates the use of
`collect_delvewheel_libs_directory` hook utility to collect DLLs
from `numpy.libs` directory (applicable to Windows PyPI wheels,
which have been using `delvewheel` for a while now).

Instead of checking that installer is `pip`, check that it is
not `conda`, because PyPI wheels may be installed via other
installers, such as `uv`.

Starting with `pandas` 2.1.0, their Windows PyPI wheels have been
using `delvewheel` to put DLLs into external `pandas.libs` directory.

Up until now, the bundled copy of `msvcp140-*.dll` seems to have
been picked up automatically by binary dependency analysis;
however, it is more future-proof to explicitly ensure that the
external `pandas.libs` directory is collected by using the
`collect_delvewheel_libs_directory` hook utility function.

…9366)

…9369)

Add missing `importorskip('pkg_resources')` decorators to all
tests that use `pkg_resources.declare_namespace()` function,
and therefore require `pkg_resources`, which was removed in
`setuptools` 82.0.0.

Port the remaining metadata tests that were using `pkg_resources`
(`test_single_file_metadata` and `test_collect_entry_point`) to
`importlib.metadata`.

Extend the work-around for broken `setuptools` upgrade to also
cover `pkg_resources`, which was removed in `setuptools` 82.0.0;
and the defunct namespace package arising from the left-over
`pkg_resources` directory (caused by `.opt-1.pyc` in `__pycache__`
directory of initial `setuptools` installation that `pip` fails
to remove) is wreaking havoc in our tests.

Looks like the issue with broken `setuptools` upgrade is now also
manifesting in the `cygwin` workflow, so add the work-around step
to mitigate it.

This is a simplified version of what we use in the "tests" job
that targets only `pkg_resources`, which is the only problematic
part in `cygwin` workflow.

We can probably remove it once cygwin python installation includes
`setuptools` >= 82.0.0 by default.