`edc-extensions/bdrs-client` multi-tenancy feature

[matbmoser]

WHAT

Modules	Description	Ready?	Relevance	Notes
edc-extensions/bdrs-client	registers an AudienceMapper that will use the BDRS to map between BPNLs and DIDs	❌/✅	Standard Compliance	Is not participant aware, but potentially does not have to be, as there is no value in storing the mapping data redundantly and there is no record on which participant uses which mappings

WHY

As specified in #2683 we need to do some "changes" to the EDC extensions in order for it to be fully multi-tenancy aware.

HOW

Replicating the behavior observed in the upstream EDC multi-tentancy modules which are aware of the participantId in the api context. Utilizing UUIDs similar to what is done in the tractusx-identity-hub.

[lgblaumeiser]

Hi @matbmoser , that is actually not a good example, because the topic is, that the bdrs client most likely only needs to be supported as one instance. There is no value added in keeping the data as multiple redundant copies.

But it makes sense to understand, what it does and to check whether there is still a need for some adaptations.