Bump pyinstaller from 6.5.0 to 6.6.0 in the python-dependencies group

[dependabot]

Bumps the python-dependencies group with 1 update: pyinstaller.

Updates pyinstaller from 6.5.0 to 6.6.0

Release notes

Sourced from pyinstaller's releases.

v6.6.0

Please see the v6.6.0 section of the changelog for a list of the changes since v6.5.0.

Changelog

Sourced from pyinstaller's changelog.

6.6.0 (2024-04-13)

Features

* (Windows) Implement support for resolving executable's true location
  when launched via a symbolic link. (:issue:`8300`)
* Implement an option to explicitly specify the bytecode optimization level
  for collected python code, independent of the optimization level in the
  python process under which PyInstaller is running. At the .spec file level,
  this is controlled by optional ``optimize`` argument in the ``Analysis``
  constructor. At the CLI level, this is controlled by new
  :option:`--optimize` command-line option, which sets the ``optimize``
  argument for ``Analysis`` as well as :ref:`interpreter run-time options
  <specifying python interpreter options>` in the generated spec file.
  See :ref:`bytecode optimization level` for details. (:issue:`8252`)
Bugfix

* (macOS) Explicitly convert the value of ``version`` argument to ``BUNDLE``
  into a string, in order to mitigate cases when user accidentally enters
  an integer or a float. The version value ends up being written to
  ``Info.plist`` as the ``CFBundleShortVersionString`` entry, and if this
  entry is not of a string type (for example, is an integer), the
  generated .app bundle crashes at start. (:issue:`4466`)
* (Windows) Avoid trying to import ``PySimpleGUI`` in the subprocess that
  analyzes dynamic library search modifications made by packages prior to
  the binary dependency analysis. When imported for the first time,
  ``PySimpleGUI`` 5.x displays a &quot;first-run&quot; dialog, which poses a problem
  for unattended PyInstaller builds running in a clean environment, for
  example, in a CI pipeline. (:issue:`8396`)
* (Windows) Implement a work-around for running PyInstaller under python
  process with ``-OO`` (or ``PYTHONOPTIMIZE=2``) with ``cffi`` installed.
  We now temporarily disable import of ``cffi`` while importing
  ``pywin32-ctypes`` in ``PyInstaller.compat`` to ensure that ``ctypes``
  backend is always used, as the ``cffi`` backend uses ``pycparser`` and
  requires docstrings, which makes it incompatible with the ``-OO`` mode.
  (:issue:`6345`)
Hooks

* Update ``PySide6.Qt3DRender`` hook for compatibility with ``PySide6``
  6.7.0 (add hidden import for ``PySide6.QtOpenGL`` module). (:issue:`8404`)
* Update ``scipy.special._ufuncs`` hook for compatibility with SciPy 1.13.0
  (add ``scipy.special._cdflib`` to hidden imports). (:issue:`8394`)
&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt; 
&lt;/code&gt;&lt;/pre&gt;
&lt;/blockquote&gt;
&lt;p&gt;... (truncated)&lt;/p&gt;
&lt;/details&gt;
&lt;details&gt;
&lt;summary&gt;Commits&lt;/summary&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/pyinstaller/pyinstaller/commit/5d7a0449ecea400eccbbb30d5fcef27d72f8f75d&quot;&gt;&lt;code&gt;5d7a044&lt;/code&gt;&lt;/a&gt; Release v6.6.0. [skip ci]&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/pyinstaller/pyinstaller/commit/edf1694e2d06866fe027439aaba3d62dba5f2b86&quot;&gt;&lt;code&gt;edf1694&lt;/code&gt;&lt;/a&gt; hooks: PySide6.Qt3DRender: add hiddenimport of PySide6.QtOpenGL&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/pyinstaller/pyinstaller/commit/1964b413378e6da9d499a476304c2165925dbef5&quot;&gt;&lt;code&gt;1964b41&lt;/code&gt;&lt;/a&gt; tests: bump PySide6 to 6.7.0&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/pyinstaller/pyinstaller/commit/4f194dc2411b9e1b33d8673ea6c4f95df4af6884&quot;&gt;&lt;code&gt;4f194dc&lt;/code&gt;&lt;/a&gt; building: avoid importing PySimpleGUI prior to binary dep. analysis&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/pyinstaller/pyinstaller/commit/5fe069177c9fda8ae7e362cdaa5b39c5b64fe4f5&quot;&gt;&lt;code&gt;5fe0691&lt;/code&gt;&lt;/a&gt; hooks: update scipy.special._ufuncs hook for SciPy &amp;gt;= 1.13.0&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/pyinstaller/pyinstaller/commit/6dbafa1f2f7b1c2f6c8c49242367514a986fa511&quot;&gt;&lt;code&gt;6dbafa1&lt;/code&gt;&lt;/a&gt; Tests: Requirements: Scheduled weekly dependency update for week 14 (&lt;a href=&quot;https://redirect.github.com/pyinstaller/pyinstaller/issues/8394&quot;&gt;#8394&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/pyinstaller/pyinstaller/commit/3fd6f5d1d5e162b28845a9e325e0d2474262969b&quot;&gt;&lt;code&gt;3fd6f5d&lt;/code&gt;&lt;/a&gt; doc: extend documentation on temporary directory for onefile programs&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/pyinstaller/pyinstaller/commit/e8dac24c866e0cc3284ca44b716b5e6f2fb04284&quot;&gt;&lt;code&gt;e8dac24&lt;/code&gt;&lt;/a&gt; tests: add a test for bootloader fully resolving symlinked executable&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/pyinstaller/pyinstaller/commit/3b219631c1f81db3fe197d1e8d80660d8654a82b&quot;&gt;&lt;code&gt;3b21963&lt;/code&gt;&lt;/a&gt; bootloader: remove extended path indicator from resolved symbolic link&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://github.com/pyinstaller/pyinstaller/commit/ae69efa818e7ff92c1a889d9e56f30cca0c1eac4&quot;&gt;&lt;code&gt;ae69efa&lt;/code&gt;&lt;/a&gt; bootloader: resolve symlinks in Windows codepath of pyi_path_resolve&lt;/li&gt;
&lt;li&gt;Additional commits viewable in &lt;a href=&quot;https://github.com/pyinstaller/pyinstaller/compare/v6.5.0...v6.6.0&quot;&gt;compare view&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/details&gt;

&lt;br /&gt;
</code></pre>


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pyinstaller&package-manager=pip&previous-version=6.5.0&new-version=6.6.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 <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions


</details>