Feature/multiple datasinks

[jannisjung]

This PR is built upon PR #300 Adds support for multiple datasinks in one route

Userstory:

As a data integrator
I want to integrate a single datasource with multiple properties
so that I can break down complex data objects into single SMEs

Rules:

• Only one Data point per datasource is in scope (multiple datapoints from same datasource in separate outputs is not in scope)

Changes

• reworks routes configuration
  • adds optional attribute datasinkMappingConfiguration to routes.json
  • this maps a datasink (as key) to an array of dataTransformers (as value)
  • datasinks and -transformers additionally should be defined as before seperate arrays (to avoid breaking changes)
  • If there were specifiedmore data sinks in the array than in the datasinkMappingConfiguration, these sinks receive the unmodified data from the datasource
  • If there were specifiedmore dataTransformers in the array than in the datasinkMappingConfiguration the additional data transforers are ignored.
  • If no datasinkMappingConfiguration is provided, all provided data transfoemer will be applyed equally for each datasink.

Example Configuration:

[
	{
		"datasource": "mqttSource",
		"transformers": 
		[
			"transformer1",
			"transformer2",
			"transformer3"
		],
		"datasinks":
		[
			"sink1",
			"sink2",
			"sink3"		],
		"datasinkMappingConfiguration":
		{
			"sink1": ["transformer1"],
			"sink2": ["transformer2"],
			"sink3": ["transformer2", "transformer3"]
		},
		"trigger": "event"
	}
]

[aaronzi]

Please revert cosmetic changes

[aaronzi]

Please readd this to close the client

[aaronzi]

Looks good to me 👍🏻
The only thing I don't agree with are the cosmetic changes (even tho we have the BaSyx formatter).
For that I am referring to our code of conduct:
https://github.com/eclipse-basyx/basyx-applications/blob/main/.github/CONTRIBUTING.md#did-you-fix-whitespace-format-code-or-make-a-purely-cosmetic-patch