build(deps): update pyinstaller requirement from <6.16,>=6.14.2 to >=6.14.2,<6.17 (#290)

Updates the requirements on
[pyinstaller](https://github.com/pyinstaller/pyinstaller) to permit the
latest version.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pyinstaller/pyinstaller/releases">pyinstaller's
releases</a>.</em></p>
<blockquote>
<h2>v6.16.0</h2>
<p>Please see the <a
href="https://pyinstaller.org/en/v6.16.0/CHANGES.html#id1">v6.16.0
section of the changelog</a> for a list of the changes since
v6.15.0.</p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/pyinstaller/pyinstaller/blob/develop/doc/CHANGES.rst">pyinstaller's
changelog</a>.</em></p>
<blockquote>
<h2>6.16.0 (2025-09-13)</h2>
<p>Features</p>
<pre><code>
* (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 &quot;d&quot;
suffix,
  free-thread build with &quot;t&quot; suffix, combination of both).
<p>On Windows, the loaded python DLL is now resolved by calling
<code>GetModuleFileName</code>
on the handle exposed by :data:<code>sys.dllhandle</code>; this applies
to python.org
Windows
builds, Anaconda python on Windows, and MSYS2 python.</p>
<p>On other platforms, first explicitly verify that shared library is
enabled,
by checking the value of <code>Py_ENABLE_SHARED</code> variable exposed
by the
<code>sysconfig</code> module. On macOS, also check if .framework bundle
is
enabled instead, which is implied by a non-empty
<code>PYTHONFRAMEWORK</code>
variable in <code>sysconfig</code>. If shared library is enabled, use
<code>INSTSONAME</code>
variable exposed by <code>sysconfig</code> module as the only source of
truth
w.r.t. its name. This works even with Debian-packaged python and
<code>astral-sh/python-build-standalone</code> POSIX builds; while they
have
their <code>python</code> executable statically linked against python
shared
library, they seem to properly set these variables.</p>
<p>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 <code>Py_ENABLE_SHARED</code> variable to be
set to <code>0</code>
(and <code>INSTSONAME</code> 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 &quot;t&quot; suffix).
&lt;/tr&gt;&lt;/table&gt;
</code></pre></p>
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/pyinstaller/pyinstaller/commit/7f2ae63f703ae27955722eac4891678b546d513a"><code>7f2ae63</code></a>
Release v6.16.0. [skip ci]</li>
<li><a
href="https://github.com/pyinstaller/pyinstaller/commit/26838344a27c93c4461a0d76f24a77a1a0da4c78"><code>2683834</code></a>
ci: move work-around for potentially broken setuptools upgrade</li>
<li><a
href="https://github.com/pyinstaller/pyinstaller/commit/383196a847af1a9faefcdcd2295c17a46dfbc850"><code>383196a</code></a>
ci: fix check for broken setuptools upgrade</li>
<li><a
href="https://github.com/pyinstaller/pyinstaller/commit/5447da7971c6e156f98f6fe96a2952ac058b00bd"><code>5447da7</code></a>
ci/test requirements: Track setuptools in
tests/requirements-libraries.txt</li>
<li><a
href="https://github.com/pyinstaller/pyinstaller/commit/95226dac821f89cd45c3f9cc4a66a542b883ee47"><code>95226da</code></a>
Remove empty pytest.ini allegedly needed by test entrypoints</li>
<li><a
href="https://github.com/pyinstaller/pyinstaller/commit/255305debec6a7f56ca4fd29ad0905cd60251359"><code>255305d</code></a>
setup: Drop questionable/pointless project keywords</li>
<li><a
href="https://github.com/pyinstaller/pyinstaller/commit/5df0f47c88465fdc25e3279813ebdcd2ba2c74cb"><code>5df0f47</code></a>
setup: Drop setuptools, move to hatchling</li>
<li><a
href="https://github.com/pyinstaller/pyinstaller/commit/100c9ce0e9c0525e6a83bbebb541f7034cea69cd"><code>100c9ce</code></a>
bootloader build: Address noisy deprecation warning from waf</li>
<li><a
href="https://github.com/pyinstaller/pyinstaller/commit/52782f8e1f8fb76084d6812c2d5f2c46b2ae071d"><code>52782f8</code></a>
release: Add retry for compiling with qemu</li>
<li><a
href="https://github.com/pyinstaller/pyinstaller/commit/9e84501bdc70c500cba7344b6698f4a2134a09b6"><code>9e84501</code></a>
Move non packaging configuration out of setup.cfg/pyproject.toml</li>
<li>Additional commits viewable in <a
href="https://github.com/pyinstaller/pyinstaller/compare/v6.14.2...v6.16.0">compare
view</a></li>
</ul>
</details>
<br />


Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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)


</details>

Author: Guts

pyproject.toml

@@ -81,7 +81,7 @@ test = [
 packaging = [
     "build>=1.2.2,<2",
     "distro==1.9.* ; sys_platform == 'linux'",
-    "pyinstaller>=6.14.2,<6.16",
+    "pyinstaller>=6.14.2,<6.17",
     "pyinstaller-hooks-contrib==2025.*",
     "pypiwin32==223 ; sys_platform == 'win32'",
 ]