Sort values in log under `get_recipe_order_and_bootstrap` and `get_recipe_order_and_bootstrap` functions.

Personne n'a encore pris cette issue.

*This is a matter of preference.*

When running consecutive builds, I myself prefer the output to be as similar as possible, thriving for 100% match - this becomes more useful when looking for difference from a former build, and reducing the "noise".
Python `set`s are a very common pitfall for this, as the order is not guaranteed, so for running the same build twice you would get the log `Will compile for the following archs: arm64-v8a, armeabi-v7a` and right after it `Will compile for the following archs: armeabi-v7a, arm64-v8a`.
Same "issue" with the log `Dist will also contain modules (pillow~=10.1, kivymd~=1.1, kivy~=2.2) installed from pip` vs `Dist will also contain modules (kivy~=2.2, pillow~=10.1, kivymd~=1.1) installed from pip`.

The fix is as easy as swapping the `list` to `sorted`, would gladly open the PR myself, but first would like to get some feedback as for whether it matters to anyone besides me, or this issue is a nuisance.

> Side note: There can be more places with the same "issue", if this issue is accepted, possibly more PRs would follow.

https://github.com/kivy/python-for-android/blob/436d5a93282dcfcc7027d19d70963c6773544434/pythonforandroid/build.py#L396-L407
https://github.com/kivy/python-for-android/blob/436d5a93282dcfcc7027d19d70963c6773544434/pythonforandroid/graph.py#L340

Commencez par les sections liées de pythonforandroid/build.py (lines 396-407) et de pythonforandroid/graph.py (line 340), puis examinez comment les valeurs d’architecture et de module consignées sont collectées. Reproduisez des builds consécutifs et confirmez que les entrées de log concernées utilisent un ordre stable sans modifier leur contenu.

Rédigé par le modèle d'indexation à partir du texte de l'issue.