fix: Use correct JSON-LD context prefix

[leandro-cavalcante]

Description

In the returned policies, the policy hub adds the https://w3id.org/catenax/v0.0.1/ns/ context with the cx prefix, but then uses the cx-policy prefix instead.

Why

The cx-policy prefix isn’t bound to any context within the JSON-LD document and therefore will fail to expand during serialization.

Issue

N/A

Issue

Link to Github issue.

Checklist

Please delete options that are not relevant.

• I have followed the contributing guidelines
• I have performed IP checks for added or updated 3rd party libraries
• I have created and linked IP issues or requested their creation by a committer
• I have performed a self-review of my own code
• I have successfully tested my changes locally
• I have added tests that prove my changes work
• I have checked that new and existing tests pass locally with my changes
• I have commented my code, particularly in hard-to-understand areas
• I have added copyright and license headers, footers (for .md files) or files (for images)

[leandro-cavalcante]

@evegufy the PR #232 was closed due some issues I had within my branch. I opened this one and it already has the changes requested by @Phil91

[MaximilianHauer]

@leandro-cavalcante please refer to the policy standard of catena-x

https://catenax-ev.github.io/docs/standards/CX-0018-DataspaceConnectivity

i assume we would need to adjust the url regarding the cx-profile prefix

Catena-X ODRL Profile To clearly identify the relevant Catena-X ODRL Profile, every policy (and their subclasses) MUST use the ODRL ‘profile’ property with an IRI referring to the Catena-X ODRL Profile as defined in [ODRL policy](https://www.w3.org/TR/odrl-model/#policy) The current version is: https://w3id.org/catenax/policy/profile2405 or in compact form: cx-policy:profile2405.

[ntruchsess]

@leandro-cavalcante please also solve the conflicts

[ntruchsess]

please fix the conflicts doing a rebase on upstream main. Your pull-request should not contain anything on the 'Files changed' page that is already present in the target-branch.

[leandro-cavalcante]

@leandro-cavalcante please also solve the conflicts

I will open a new PR with the necessary changes, I'm doing the rebase but the other commits are coming together and I do not have the option to drop them.

[ntruchsess]

@leandro-cavalcante I did remove the redundant commits leaving the conflict on your actual change. Please be aware that I did a force-push to do so. Of course you may also open a new PR reapplying your change to latest main if that is more easy for you.

[leandro-cavalcante]

@leandro-cavalcante I did remove the redundant commits leaving the conflict on your actual change. Please be aware that I did a force-push to do so. Of course you may also open a new PR reapplying your change to latest main if that is more easy for you.

Thank you!

[ntruchsess]

@leandro-cavalcante to ensure a PR would not contain any unintended changes in the swagger-documentation one always needs run 'dotnet build' on the respective service module after rebase on main to regenerate the swagger (hub-service.yaml). Just did that for you but keep in mind for your next PR.

[ntruchsess]

i assume we would need to adjust the url regarding the cx-profile prefix
@MaximilianHauer : I agree - the iri specified should be adjusted as well. From my point of view this can be done independent from the current change which fixes the technical inconsistency of namespace declaration and usage being inconsistent.
I therefore merge this PR - fixing the other issues should be done in separate PR(s).
(it's not only the iri that is incorrect - the generated json-ld also doesn't contain the 'profile' property that would refer to the profile-version being in use)