Make Launcher parameters configurable remotely

[TSchmiedlechner]

User story

As a user of the Middleware Launcher, I want to be able to change relevant parts of the configuration via the fiskaltrust.Portal, so that I can alter the config without requiring to connect to the POS system.

Context

As of now, it's only possible to set the Launcher's config locally via files or parameters. It might be helpful for users to set specific parts of the config remotely, e.g. via the Portal or an API, and have it synced to the local MW frequently, to e.g. enable verbose logging in case of issues.

We'd need to clarify how the configuration would be synced than - this could either be done via a Helper package, or directly be built into the Launcher.

[volllly]

Also we need to think about precedence.
Which config overwrites which.

My suggestion is that the online configuration is overwriting the local configuration and the cli arguments overwrite both.
If we do it like that when trying something locally the cli arguments have the last word. But when you want to change config from the portal the online config has the last word.

[volllly]

First we'll need to store the online launcher configuration for each cashbox and create a way to edit the launcher configuration in the Portal.

Second we'll need to think about how to get it to the launcher.

• Option 1: Deliver it through the cashbox configuration.
• Option 2: Deliver it on its own through the configuration service.