Bump pyinstaller from 6.0.0 to 6.1.0

[dependabot]

Bumps pyinstaller from 6.0.0 to 6.1.0.

Release notes

Sourced from pyinstaller's releases.

v6.1.0

Please see the v6.1.0 section of the changelog for a list of the changes since v6.0.0.

Changelog

Sourced from pyinstaller's changelog.

6.1.0 (2023-10-13)

Features

* Allow users to re-enable the old onedir layout (without contents directory) by
  settings the :option:`--contents-directory` option (or the equivalent
  ``contents_directory`` argument to ``EXE`` in the .spec file) to ``'.'``.
  (:issue:`7968`)
Bugfix

* (macOS) Prevent bootloader from clearing ``DYLD_*`` environment variables
  when running in ``onefile`` mode, in order to make behavior consistent
  with ``onedir`` mode. (:issue:`7973`)
* (Windows) Fix unintentional randomization of library search path order
  in the binary dependency analysis step. The incorrect order of search
  paths would result in defunct builds when using both ``pywin32``
  and ``PyQt5``, ``PyQt6``, ``PySide2``, or ``PySide6``, as it would prevent
  the python's copy of ``VCRUNTIME140_1.dll`` from being collected into
  the top-level application directory due to it being shadowed by the
  Qt-provided copy. Consequently, the application would fail with
  ``ImportError: DLL load failed while importing pywintypes: The specified
  module could not be found.`` (:issue:`7978`)
* Ensure that ``__main__`` is always in the list of modules to exclude,
  to prevent a program or a library that attempts to import ``__main__``
  from pulling PyInstaller itself into frozen application bundle.
  (:issue:`7956`)
* Fix :func:`PyInstaller.utils.hooks.collect_entry_point` so that it returns
  module names (without class names). This matches the behavior of previous
  PyInstaller versions that regressed in PyInstaller ``v6.0.0`` during
  transition from ``pkg_resources`` to ``importlib.metadata``. (:issue:`7958`)
* Fix ``TypeError: process_collected_binary() got an unexpected keyword
  argument 'strip'`` error when UPX compression is enabled. (:issue:`7998`)
* Validate binaries returned by analysis of ``ctypes`` calls in collected
  modules; the analysis might return files that are in ``PATH`` but are
  not binaries, which then cause errors during binary dependency analysis.
  An example of such problematic case is the ``gmsh`` package on Windows,
  where ``ctypes.util.find_library('gmsh')`` ends up resolving the python
  script called ``gmsh`` in the environment's Scripts directory.
  (:issue:`7984`)
Hooks

* Update ``PySide6.QtHttpServer`` hook for compatibility with ``PySide6``
</tr></table> 
</code></pre>
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>

<ul>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/362ff1b9090748839b1d19f50c78abc79c1039b0"><code>362ff1b</code></a> Release v6.1.0. [skip ci]</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/89cb2043d390f21c556102a4e2356e45e0bb6cbc"><code>89cb204</code></a> Fix TypeError when using UPX compression.</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/e7c252573f424ad9b79169ab01229d27599004b1"><code>e7c2525</code></a> Tests: Requirements: Scheduled weekly dependency update for week 41 (<a href="https://github.com/pyinstaller/pyinstaller/issues/7993">#7993</a>)</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/90c2cf9137fedcfda6e42fc94d41cac4527b465b"><code>90c2cf9</code></a> hooks: update PySide6.QtHttpServer hook for PySide6 6.5.3</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/c1d5e6a8bcf4ee21d9d12a186dda76b0a2f7d06e"><code>c1d5e6a</code></a> docs: fix documentation for python interpreter run-time options [skip ci]</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/43f3d06bc582471fa27a484d189e3688c32a8573"><code>43f3d06</code></a> building: validate binaries returned by analysis of ctypes calls</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/73d2c0f8c17f61c7f219edd5ce2f2c90530b2e7a"><code>73d2c0f</code></a> bootloader: cleanup: make set_systemd_env() in pyi_utils static</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/ec2db2cbd2708127b291d8f7f54d0b6293986292"><code>ec2db2c</code></a> bootloader: cleanup: remove PYI_NULLCHAR</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/f09d20bfa80eb378984a92fc63cb845563f66a20"><code>f09d20b</code></a> bootloader: cleanup: replace pyi_utils_set_environment</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/5b7171663aa3dc1eec7ba3b9fe9cc1e7fe7caf43"><code>5b71716</code></a> bootloader: macOS: do not unset DYLD_* environment variables</li>
<li>Additional commits viewable in <a href="https://github.com/pyinstaller/pyinstaller/compare/v6.0.0...v6.1.0">compare view</a></li>
</ul>
</details>

<br />
</code></pre>


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pyinstaller&package-manager=pip&previous-version=6.0.0&new-version=6.1.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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>