Import / Export setting workflow refinement

[AJolly]

Is this a feature relevant to companion itself, and not a module?

• I believe this to be a feature for companion, not a module

Is there an existing issue for this?

• I have searched the existing issues

Describe the feature

I would like to speed up the export import setting workflow:

1. Don't force the user to go through the startup configure wizard every time you import settings

2. Remember all settings as part of the export and import. For example, surface detection, button grid size, remote services, password, etc.

3. I'd love if we could move to using json to hold the settings, rather than the sqlite.db (I understand why this may not be desired)

Usecases

I run companion on my laptop and desktop. I'm treating it as a faster replacement for stream deck software.
I would like to keep my settings synchronized between the two.
I frequently import and export my config between the two machines.

This takes much longer than required:

1. There should be no reason to force a user to go through the config wizard every time they import the configure, after all importing a configuration implies that they've already been using companion and shouldn't need to go through the entire process.

2. there is no reason the import export should not include surfaces and all settings. this is especially confusing considering import/exporting the config specifically asks you if you want to export surfaces.

3. I'd love json just because it'd be easier to synchronize between machines, (synchronization software is much better at dealing with json to resolve conflicts).

4. Copy Paste of buttons in json format (ie, let me easily copy paste a button between pcs, or browser tabs)

[Julusian]

1. & 2) There is a draft PR that should resolve most/all of this part feat: add userconfig to import-export #2875

2. We have only changed the db to be sqlite (feat: Migrate to SQLite #3045), not yet in a stable release. This was done partly in a new effort to mitigate corruption reported by some windows users, also because some peoples configs are becoming longer than nodejs can store in a string making their configs unreadable, and to minimise the cost of making config changes, to minimise the amount of data we write to disk.