Store app data in a dedicated path for development and test environments

[sorsaffari]

At the moment, the app data such as favourite queries and query settings are stored within the default path for Workbase running in production, development or test environments. Ideally, each Workbase running in each environment should use an isolated data file where changes made in it are not reflected in any subsequent initializations of the app.

This will allow us to modify the content of the app data or even remove it altogether for each environment without affecting the app state in the other environments.

[alexjpwalker]

Once we use app data for... well, anything, really, we should test how this is handled in Studio.

[alexjpwalker]

Now that we've implemented app data, I have to say that it's quite handy that it gets persisted between dev runs. The main things we want to store are the last-connected server address and the last-opened project directory.

Nonetheless, it's pretty counterintuitive that the TypeDB Studio production distribution uses the same app data directory as the dev distribution. Maybe create a dev subfolder of the app data directory and use that when running in dev mode (i.e via bazel run //:studio-bin-mac?