Show/edit/Save connection

[pierre-yves-monnet]

The connection to Zeebe is on the property file.

This is boring because it is impossible to use a docker image "as is" without changing the image and the property file.
Idea is:

• when the property file is empty, and no Zeebe configuration is given, the framework starts and publishes red information on the dashboard page
• user access a tab "property". The configuration to connect is visible on that page
• user can set information to connect. Framework can connect
  This information must be saved in a local (H2) database. Next restart, information will be present.

At any time, the user can come to see / edit information about the connection.

[jonathanlukas]

I would imagine this as either/or, also for security reasons:

If I provide a static connection by injecting env variables or enhancing the configuration, I do not want this connection to change.

If I do not provide any connection information, I want this to be dynamic.

Or, you could introduce a switch that enables dynamic connection configuration and is disabled by default.