feat: Portable GUI config directory

[FibreTTP]

Feature description

Related: #118

Allow portability of the morphe-gui config directory, perhaps by testing for a directory named morphe-gui next to the binary.

Motivation

I use Morphe CLI (the GUI) on multiple computers, and would like to skip the step of having to copy and replace the config directory in AppData each time I use it on a different computer.

Acknowledgements

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

[prateek-who]

I was testing this. Moving away from AppData and having everything in the .jar file's folder seems so much better for portability.

[FibreTTP]

Referencing work done in #145.

The config directory is created next to the binary now, that's good. But the config.json still writes absolute paths to the patched APKs directory and the keystore file, even if they are also in the same directory as the binary. This doesn't make it fully portable yet.

I've tested manually editing the config.json file to only include the basename of both, for example:

{
  "defaultOutputDirectory": "patched-apks",
  "keystorePath": "urv_keystore.keystore"
}

And this works. It correctly reads the keystore, and correctly writes the patched APK into that directory.

Could it be possible for Morphe to detect if the path chosen by the user is either directly next to the binary, or in a path below it, and write the relative path instead?

Also, when relative paths are used, do you know if they're calculated relative to the binary, or the CWD?

[prateek-who]

https://github.com/MorpheApp/morphe-cli/suites/69782496267/artifacts/7094542349

Try this and see once. We now resolve against the binary directory.