Runtime dependencies are based on dependency packages

[iLLiCiTiT]

Changelog Description

Remove dependency packages that should be defined by ayon-core/openpype addon and use runtime dependencies from dependency package.

Additional info

This PR will be combination of PRs in multiple repositories (OpenPype, ayon-dependencies-tool, ayon-launcher).

• ayon-launcher
• ayon-dependencies-tool
• OpenPype

Testing notes:

1. Create ayon-launcher installer with this PR
2. Upload installer to server
3. Upload OpenPype addon with required change
4. Create a bundle with the installer and OpenPype addon
5. Create dependency package for the bundle and use it in the bundle
6. Run ayon-launcher with the bundle
7. All should be working

[BigRoy]

Remove dependency packages that should be defined by ayon-core/openpype addon and use runtime dependencies from dependency package.

Could you elaborate why this must be the case?

The way I understand it: These are not dependencies to the launcher, but are dependencies to OpenPype addon.

However, what makes it a runtime dependency? At what runtime? For the launcher? For a host application? When/where do these dependencies get injected to what environment? Does this PR solve e.g. the Houdini 20 issues for PIL?

[iLLiCiTiT]

Could you elaborate why this must be the case?

In sum, runtime dependencies are available only in ayon-launcher process, and are not added to PYTHONPATH. The removed ones are not required by ayon-launcher to work, but are required by openpype addon.

Does this PR solve e.g. the ynput/OpenPype#5921 (comment)?

It should (but Pillow was already in runtime dependencies for AYON).

[kalisp]

Runtime dependencies (PIL, OTIO) are moved to dependency package and not launcher.