AAS Gateway - Create Configuration Logic

[FriedJannik]

Currently:

Specified AAS Environment Files are loaded and published to hard coded Servers

Goal:

Instead of only configuring files to load, also configure where to upload the files in this scheme (separate file, e.g. preconfiguration-mapping.json) :

If no endpoints are specified for an environment file, the default values are used.
NOTE: If no default is defined for the registry URL and no value is set in the mapping, there is no registry integration for that file.

application.properties

• basyx.client.defaults.aas-repository (required)
• basyx.client.defaults.submodel-repository (required)
• basyx.client.defaults.aas-registry (optional)
• basyx.client.defaults.submodel- registry (optional)

[FriedJannik]

Belongs to #447

[mdanish98]

#450 -> Related ticket