Improve namespace prefixes configuration

[wolf4ood]

Feature Request

Allow custom prefixes to be configured with EDC configurations without requiring a custom extension.

Which Areas Would Be Affected?

JsonLDExtension

Why Is the Feature Desired?

Currently it's possible only to configure cached document but if users wants to support custom namespace prefixes an extension is required.

Solution Proposal

Implement a new configuration in JsonLdExtension that read a configuration and register custom namespaces.

Example of configuration:

edc.jsonld.namespace.customns.scopes=MANAGEMENT_API
edc.jsonld.namespace.customns.iri=http://www.w3.org/ns/odrl/2/
edc.jsonld.namespace.customns.prefix=customprefix
edc.jsonld.namespace.customns.enabled=true

the enabled flag seems useless, but it can be used to override registered context via extensions.

This allow having a clean response for people who wants to bring their own context definition and remove the usage of prefix namespace mapping.

For example currently when using the extension management-api-json-ld-context is used, which is an experimental context definition for the EDC management API all the response will contain a @context like this:

{
    "@context": [
        "https://w3id.org/edc/connector/management/v0.0.1",
        {
            "@vocab": "https://w3id.org/edc/v0.0.1/ns/",
            "edc": "https://w3id.org/edc/v0.0.1/ns/",
            "odrl": "http://www.w3.org/ns/odrl/2/"
        }
    ]
}

which is not ideal.

[wolf4ood]

Not relevant, the improvements will be done manually via #4466