Better support for multiple dataset names

[erlendoksvoll]

Description

In order to easier be able to reuse datasets and integrations between service contexts, evidencecodes should support an alias list in the evidence code model.

Maybe List<string, string> datasetAliases => servicecontext, nameOfDataset in order to allow filtering and renaming depending on context

Core needs to be able to look for both evidence code names and aliases from getavailableevidencecodes when validation requests and also correctly route to the correct name when communication with the plugin.

Extend the evidencecode model to include "DatasetAliases" and apply a filtering when validating an authorization request and make sure the consumers use the relevant dataset name - if an alias(es) exists for the servicecontext, then these must be used.
Filter out irrelevant servicecontexts from metadata and Core should always route to the evidencecodename - i.e. the name of the function.

Additional Information

No response

Tasks

No response