Bump pyinstaller from 5.2 to 5.3

[dependabot]

Bumps pyinstaller from 5.2 to 5.3.

Release notes

Sourced from pyinstaller's releases.

v5.3

Please see the v5.3 section of the changelog for a list of the changes since v5.2.

Changelog

Sourced from pyinstaller's changelog.

5.3 (2022-07-30)

Features

* (Windows) Implement handling of console control signals in the ``onefile``
  bootloader parent process. The implemented handler suppresses the
  ``CTRL_C_EVENT`` and ``CTRL_BREAK_EVENT`` to let the child process
  deal with them as they see it fit. In the case of ``CTRL_CLOSE_EVENT``,
  ``CTRL_LOGOFF_EVENT``, or ``CTRL_SHUTDOWN_EVENT``, the handler attempts
  to delay the termination of the parent process in order to buy time for
  the child process to exit and for the main thread of the parent process
  to clean up the temporary directory before exiting itself. This should
  prevent the temporary directory of a ``onefile`` frozen application
  being left behind when the user closes the console window. (:issue:`6591`)
* Implement a mechanism for controlling the collection mode of modules and
  packages, with granularity ranging from top-level packages to individual
  sub-modules. Therefore, the hooks can now specify whether the hooked
  package should be collected as byte-compiled .pyc modules into embedded
  PYZ archive (the default behavior), or as source .py files collected as
  external data files (without corresponding modules in the PYZ archive).
  (:issue:`6945`)
Bugfix

* (non-Windows) Avoid generating debug messages in POSIX signal handlers,
  as the functions involved are generally not signal-safe. Should also
  fix the endless spam of ``SIGPIPE`` that ocurrs under certain conditions
  when shutting down the frozen application on linux. (:issue:`5270`)
* (non-Windows) If the child process of a ``onefile`` frozen application
  is terminated by a signal, delay re-raising of the signal in the parent
  process until after the clean up has been performed. This prevents
  ``onefile`` frozen applications from leaving behind their unpacked
  temporary directories when either the parent or the child process is
  sent the ``SIGTERM`` signal. (:issue:`2379`)
* When building with ``noarchive=True`` (e.g., ``--debug noarchive`` or
  ``--debug all``), PyInstaller no longer pollutes user-writable source
  locations with its ``.pyc`` or ``.pyo`` files written next to the
  corresponding source files. (:issue:`6591`)
* When building with ``noarchive=True`` (e.g., ``--debug noarchive`` or
  ``--debug all``), the source paths are now stripped from the collected
  .pyc modules, same as if PYZ archive was used. (:issue:`6591`)
Hooks

</tr></table> 
</code></pre>
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>

<ul>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/fbf7948be85177dd44b41217e9f039e1d176de6b"><code>fbf7948</code></a> Release 5.3.</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/ba38ba4ba90ae726129e15240f25c27ddc29bf29"><code>ba38ba4</code></a> tests: put pyi_builder's clean-up under environment variable switch</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/acf10bb7c6c31cef8abee63fa73adbed926de003"><code>acf10bb</code></a> tests: have pyi_builder fixure clean up directories on Windows</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/2fa0497783aab41800620961f166628e2b915ae8"><code>2fa0497</code></a> tests: modulegraph unit tests: do not use distutils as test package</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/6ccba969db1fe7fa43c0bbd0bdb224c7775c3e70"><code>6ccba96</code></a> tests: test_import_pep302: do not use distutils as test package</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/dfdf7f9db172ce938fce3bd78c833b44f07e2e81"><code>dfdf7f9</code></a> tests: test_apple_event_handling_carbon: ensure unique app path</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/5b9e61fca052e59fdb2533f6406fa457a65cb0ce"><code>5b9e61f</code></a> tests: test_pkg_resources_provider: include uuid in generated egg path</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/7875d7684c6ddad90e91af9141229083ebb1297f"><code>7875d76</code></a> compat: remove obsolete compatibility definitions</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/6cb49d9050e1b7a5142f7b9142f5cc7bde31ee31"><code>6cb49d9</code></a> loader: remove delayed imports from pymod02_importers</li>
<li><a href="https://github.com/pyinstaller/pyinstaller/commit/c115bce4dd1eb43c3e1ad52ca6743ed6fd3f0a70"><code>c115bce</code></a> loader: remove pyimod01_os_path and replace its use with os.path</li>
<li>Additional commits viewable in <a href="https://github.com/pyinstaller/pyinstaller/compare/v5.2...v5.3">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=5.2&new-version=5.3)](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 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>