feat: Create cli options to export both patches and options to JSON and set options from JSON during pathing

[jdelange22]

Feature description

Just as inotia00 did on the RVX fork of the revanced cli, it would be conveniant to have the options to export patches and options to JSON format so they can be used in cli wrappers like the NodeJS rvx-builder. Also setting the options from the generated options.json would be a nice feature that I'm currently missing in the morphe cli. I used the rvx builder a lot running it on my phone inside Termux but without these features it is way to hard to adjust the builder to use Morphe.

Motivation

• Conveniant features for cli wrappers
• Makes it possible to create a "morphe-builder" NodeJS app
• Fairly easy to implement

Acknowledgements

• I have checked all open and closed feature requests and this is not a duplicate.
• I have chosen an appropriate title.

[prateek-who]

Essentially a flag needs to be added to the CLI? You run the CLI with this flag and it generates a .json file that holds all the patch versions and their options right?

[LisoUseInAIKyrios]

Patch versions may change and should not be part of any user saved json.

The prior/current CLI documentation says multiple patch bundles can be used. Each bundle should have own patch namespace because two unrelated patch bundles can both have the a patch named "Hide ads". So patch options could be configured independently and multiple patch jsons should be allowed. This all makes sense and is how Manger functions with multiple bundles.

But, as far as I can tell the CLI functionality to use multiple bundles does not work:
java -Xms1024m -jar morphe-cli*-all.jar patch --patches *mpp ---out morphe.apk
Only uses the first mpp file in the path and ignores all others.

java -Xms1024m -jar morphe-cli*-all.jar patch --patches other.mpp patches-1.12.0-dev.2.mpp ---out morphe.apk
Gives a CLI command line argument error.

java -Xms1024m -jar morphe-cli*-all.jar patch --patches patches-1.12.0-dev.2.mpp --patches other.mpp ---out morphe.apk
Always uses the first --patches argument and ignores the second.

The code itself doesn't seem to have any logic to load multiple bundles. So it seems this functionality was never actually implemented, unless somehow multiple patch bundles are loaded thru some undocumented esoteric way.

[LisoUseInAIKyrios]

If Inotia CLI has this feature, then please identify what commits or what code does this.

[jdelange22]

See commit below for patches.json generation:
inotia00/revanced-cli@054bdac
And this later commit renamed the cli command from 'json' to 'patches':
inotia00/revanced-cli@c696e33

See commit below for options.json generation:
inotia00/revanced-cli@29b6e4e

And this commit for setting patch options based on json:
inotia00/revanced-cli@9d96df3

[kitadai31]

For patches.json, Morphe already generates it when a new version is released
https://github.com/MorpheApp/morphe-patches/blob/main/patches-list.json
Wrapper software can use it
So I think the patches json generator is not necessary

On the other hand, the options json might still be useful?

[jdelange22]

Good to know Morphe provides a JSON file for patches, but it's not exactly the same as the CLI generating the JSON based on the patches. When the CLI generates the patches.json file, it is entirely based on the patches that the uses provides. These could be the current stable patches, the latest development patches or even some user-specified patches or from another source. So when the CLI generates this JSON file it is always based on the patches file provided by the user.