Problem with collecting the script that is in Python into a build (.exe)

Hello. This task is for someone who has gathered many Python projects into .EXE and has significant experience in this area. I have attached screenshots. I have the source code with various scripts. There is also a builder that compiles them into one builder (.exe). We added the library selenium-wire==5.1.0 to the general scripts, and errors and warnings occur during the build process. An interesting fact! The project is large, built with over 50 different libraries, and there were no such conflicts. I also note that there is regular Selenium, which was built without issues, as well as stealth, which is like a binary. In addition to the dependencies listed in the requirements.txt file for its build, I added some info with hooks, as they call it, in myapp.spec, where I wrote its paths where the library is located, and so on. And this was also built without conflicts. But this selenium-wire seems to be very special. The developer tried to remove the conflicting libraries, but that’s pointless because they are needed! When we simply updated their version, the console where the build is compiled kept cycling us, telling us to remove this, then add that, and so on, like some kind of loop. In short! My thought is that something like this: selenium-wire should not be built as a build but somehow inserted into .exe. Or it should be built correctly. Yes, in the console, there is a prompt to press enter to ignore the conflict, and everything should compile, and essentially everything should work. Because! I don’t understand at all, in the editor where the project runs, there are no conflicts. But here there are some conflicts. Unfortunately, just writing something in my 2 files that are responsible for the build and sending it back to me is unlikely to help me. Therefore, you need to connect with me, as various developers often do, and take a look at this problem. Because I definitely will not send code with various libraries and my files that are over 2 GB. That’s nonsense! Give me work here, not just writing code, but thinking and correctly specifying the conditions so that the build compiles.
Words from the specialist who created a new function for me and added the selenium wire library. 

Ensure the correct operation of the Python application using selenium-wire==5.1.0, eliminate all dependency conflicts that hinder compilation into .exe, despite the fact that the script runs correctly.

The library used:

selenium-wire==5.1.0

Also used:

httpcore==0.17.3

httpx==0.24.1

h2>=4.0

googletrans==3.1.0a0

At the script launch stage, everything works, but during the .exe build (via pyinstaller), dependency errors occur due to:

conflicts between httpx and httpcore

conflicts between versions h2 — 3.* and 4.*

googletrans, which has a faulty dependency on the outdated httpx==0.13.3 in the PyPI version

selenium-wire==5.1.0 requires:

h2 >= 4.0

And httpx==0.13.3 (faulty dependency for googletrans) requires:

httpcore==0.9.*

httpcore==0.9.* requires:

h2==3.*

Conflict: cannot use h2==4.* and h2==3.* simultaneously