build(deps): bump pyinstaller from 6.15.0 to 6.16.0

[dependabot]

Bumps pyinstaller from 6.15.0 to 6.16.0.

Release notes

Sourced from pyinstaller's releases.

v6.16.0

Please see the v6.16.0 section of the changelog for a list of the changes since v6.15.0.

Changelog

Sourced from pyinstaller's changelog.

6.16.0 (2025-09-13)

Features

* (POSIX) Adjust the destination directory for collected python's standard
  extensions, from ``lib-dynload`` to ``python3.x/lib-dynload`` directory,
  in order to preserve the relative relationship between the extension
  location and the (grand-parent) shared library directory that is commonly
  found in POSIX python environments. This is required for compatibility
  with upcoming Linux builds of ``astral-sh/python-build-standalone#`` that
  will set relative library paths in extensions via both ``DT_NEEDED`` and
  ``DT_RPATH``. (:issue:`9212`)
* Rework the anonymization of the ``co_filename`` attribute in collected
  code objects - instead of trying to obtain anonymized relative name by
  removing known path prefixes from the original absolute-path ``co_filename``,
  we now construct the anonymized relative name directly from the collected
  module's (or script's) destination name w.r.t. its destination container
  (i.e., the ``PKG`` archive, the ``PYZ`` archive, or the ``base_library.zip``
  archive). (:issue:`9226`)
* Rework the search for python shared library in order to reduce amount of
  guess-work and better accommodate variations in naming across platforms
  and due to different build options (e.g., debug build with "d" suffix,
  free-thread build with "t" suffix, combination of both).
On Windows, the loaded python DLL is now resolved by calling
GetModuleFileName
on the handle exposed by :data:sys.dllhandle; this applies to python.org
Windows
builds, Anaconda python on Windows, and MSYS2 python.
On other platforms, first explicitly verify that shared library is enabled,
by checking the value of Py_ENABLE_SHARED variable exposed by the
sysconfig module. On macOS, also check if .framework bundle is
enabled instead, which is implied by a non-empty PYTHONFRAMEWORK
variable in sysconfig. If shared library is enabled, use INSTSONAME
variable exposed by sysconfig module as the only source of truth
w.r.t. its name. This works even with Debian-packaged python and
astral-sh/python-build-standalone POSIX builds; while they have
their python executable statically linked against python shared
library, they seem to properly set these variables.
In contrast, both Linux and macOS builds of Anaconda python seem to
build their interpreter executable and python shared library separately,
so the interpreter reports Py_ENABLE_SHARED variable to be set to 0
(and INSTSONAME gives name of the static library). Therefore, for
Anaconda python on non-Windows, use the old approach of guessing the
library name from the major and minor version and whether free-threading
is enabled or not (i.e., the presence of the "t" suffix).
</tr></table>

... (truncated)

Commits

• 7f2ae63 Release v6.16.0. [skip ci]
• 2683834 ci: move work-around for potentially broken setuptools upgrade
• 383196a ci: fix check for broken setuptools upgrade
• 5447da7 ci/test requirements: Track setuptools in tests/requirements-libraries.txt
• 95226da Remove empty pytest.ini allegedly needed by test entrypoints
• 255305d setup: Drop questionable/pointless project keywords
• 5df0f47 setup: Drop setuptools, move to hatchling
• 100c9ce bootloader build: Address noisy deprecation warning from waf
• 52782f8 release: Add retry for compiling with qemu
• 9e84501 Move non packaging configuration out of setup.cfg/pyproject.toml
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[coveralls-official]

Pull Request Test Coverage Report for Build 17777646893

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 25 unchanged lines in 8 files lost coverage.
• Overall coverage decreased (-0.02%) to 91.148%

---

Files with Coverage Reduction	New Missed Lines	%
chia/full_node/full_node.py	1	87.27%
chia/server/node_discovery.py	1	82.11%
chia/_tests/simulation/test_simulation.py	1	96.47%
chia/wallet/wallet_node.py	1	87.13%
chia/timelord/timelord_launcher.py	2	89.29%
chia/rpc/rpc_server.py	3	88.4%
chia/server/address_manager.py	5	92.84%
chia/timelord/timelord.py	11	71.94%

Totals
Change from base Build 17773649562:	-0.02%
Covered Lines:	102726
Relevant Lines:	112539

---

💛 - Coveralls

[emlowe]

@dependabot rebase

[arvidn]

looks good, but it would cause a conflict with this other PR of mine :/
#20159

[arvidn]

oh, it's already in conflict :/