When enriching signals (e.g. events/messages) with extraFields, duplicate paths lead to not all fields to be enriched

[thjaeckle]

When using signal enrichment, e.g. in connections or websockets to receive additional fields to the actually changes ones, it leads to unexpected problems when e.g. selecting the following extraFields:

features/operationalMode/properties/configuration/mode
features/{{feature:id}}/properties/configuration

In this example, {{feature:id}} would also resolve to operationalMode.

We encountered that in such a case, only the first field will be enriched, the features/{{feature:id}}/properties/configuration will be ignored. Changing the order does not make a difference.

The cause is not yet really clear to me - maybe because of the {{feature:id}} placeholder or maybe because configuration/mode is a part of configuration.

Has to be investigated in order to fix.