Ability to store configs in different place

Our DevOps team said that they want to have the ability to store dbvr configurations not in a workspace (which is big and specific, in case you do not work with DBeaver all the time).
But in a different configuration file. yaml format, as an example.
The configuration source can be added as a property for the -data parameter, and loaded on the start or before it.
This yaml file can keep the connection settings. Or more.
We need to document this feature with examples after.

Start by tracing how the CLI currently reads workspace configuration and how the -data parameter is handled during startup. Define the supported external YAML configuration scope, loading timing, and connection settings, then document the completed behavior with examples.

Written by the indexing model from the issue text.