toolchain: auto resolve deps

[T-Dynamos]

Closes #3274

Package resolution is performed using the hostpython's pip via the --dry-run option.

Example

requirements = python3,
    kivy==master,
    materialyoucolor,
    materialshapes,
    exceptiongroup,
    asyncgui,
    asynckivy,
    android,
    pillow==11.0.0,
    pycairo,
    https://github.com/kivymd/KivyMD/archive/master.zip,
    trio,
    openai

Output:

[AndreMiras]

Awesome work, looks good overall, pretty clear and nice feature thank you!
I just have a few remarks and concerns I'd like to discuss.

1. It would be nice to have at least some basic unit tests for is_wheel_platform_independent() (that one should be relatively easy) and process_python_modules() (that one is more tricky, but let's try to have at least some basic coverage). I noticed the code currently bypasses the new logic when recipe_build_order is a Mock - having proper tests would let us remove that workaround.
2. Have we thought of having a --no-auto-resolve or something like that for reproducible builds?
3. A bit tricky to integration test, I imagine that would mean having an app build with the requirements list not fully defined/pinned and test it runtime, but then we have some build reproducibility concerns. Do you have some ideas for how to make sure your changes don't get broken later on without us realising?

[T-Dynamos]

@AndreMiras

A bit tricky to integration test, I imagine that would mean having an app build with the requirements list not fully defined/pinned and test it runtime, but then we have some build reproducibility concerns. Do you have some ideas for how to make sure your changes don't get broken later on without us realising?

I think an integration test would be overkill here. The modules list is highly variable, and all of this work is handled by pip itself.

[AndreMiras]

OK let's go :)