Catena-x Policy Validation file

# Overview

## Explain the topic in 2 sentences

Sub-issue of https://github.com/catenax-eV/sig-roadmap/issues/356
The goal of the Data Sovereignty Expert Group is to provide a central and maschine readable file that provides all the specifications of the allowed constraints in the catena-x context.
This then can be used as a validation reference.

## What's the benefit?

* removal of the entry barrier to understand and use constraints in the catena-x dataspace
* raising policy quality by providing a maschine readable file that can be used to validate a policy

## What are the Risks/Dependencies ?

* no risks

## Detailed explanation

As Part of the evolution of the catena-x dataspace the data sovereignty expert group is focusing on reducing the entry barrier of the policy usage and creation even further.
By providing a maschine readable file the community can use this to update their custom apps based on the newest adjustments but furthermore can validate manually created policy against it.

### Current implementation
Currently the definition is to be found in different places
* standard 0018
* repo https://github.com/catenax-eV/cx-odrl-profile

on top of this it is noticable that the current definition in the cx-ordl-profile does not fit 1:1 with the tractus-x edc implementation

### Proposed improvements

centralizing the documentation landscape to the standard 0018 and included a maschine readable file there to be found.

## Feature Team

### Contributor

- @DanielaWuensch
- @MaximilianHauer

### Committer

- Committer 1
- Committer 2

## User Stories

- Issue 1, linked to specific repository
- Issue 2, linked to another specific repository

## Acceptance Criteria

- [ ] Criteria 1
- [ ] Criteria 2
- [ ] Criteria 3

## Test Cases

### Test Case 1

#### Steps

1. Do something
2. Click something
3. Add something

#### Expected Result

1. Maschine readable file is provided that can be used for the validation of policies.

## Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented.

In the context of the standards [126](https://catenax-ev.github.io/docs/standards/CX-0126-IndustryCorePartType) and [127](https://catenax-ev.github.io/docs/standards/CX-0127-IndustryCorePartInstance), typically only one is applicable, depending on the specific use case. Please cross out one of the two standards that does not apply.

- [ ] This feature aligns with our current architectural guidelines
- **Data Sovereignty:** All data sharing activities across company boundaries follow the [Catena-X Regulatory Framework](https://catenax-ev.github.io/docs/next/regulatory-framework/governance-framework), in particular the [Data Exchange Governance](https://catenax-ev.github.io/docs/next/regulatory-framework/20000ft/data-exchange-governance), and the [Dataspace Protocol](https://docs.internationaldataspaces.org/dataspace-protocol/overview/readme) via a compliant Connector (like the [tractusx-edc](https://github.com/eclipse-tractusx/tractusx-edc) or similar, see [Connector KIT](https://eclipse-tractusx.github.io/docs-kits/next/category/connector-kit))
- [ ] [CX-0010 Business Partner Number](https://catenax-ev.github.io/docs/next/standards/CX-0010-BusinessPartnerNumber)
- [ ] [CX-0013 Identity of Member Companies](https://catenax-ev.github.io/docs/next/standards/CX-0013-IdentityOfMemberCompanies)
- [ ] [CX-0018 Data Space Connectivity (EDC)](https://catenax-ev.github.io/docs/next/standards/CX-0018-DataspaceConnectivity)
- [ ] [CX-0049 DID Document Schema](https://catenax-ev.github.io/docs/next/standards/CX-0049-DIDDocumentSchema)
- [ ] [CX-0050 Framework Agreement Credential](https://catenax-ev.github.io/docs/next/standards/CX-0050-FrameworkAgreementCredential)
- [ ] [CX-0149 Verified Company Identity](https://catenax-ev.github.io/docs/next/standards/CX-0149-Dataspaceidentityandidentification)
- **Interoperability:** Digital Twins are used (compliant to the [Digital Twin KIT](https://eclipse-tractusx.github.io/docs-kits/next/category/digital-twin-kit) and the [Industry Core KIT](https://eclipse-tractusx.github.io/docs-kits/next/category/industry-core-kit))
- [ ] [CX-0001 EDC Discovery API](https://catenax-ev.github.io/docs/next/standards/CX-0001-EDCDiscoveryAPI)
- [ ] [CX-0002 Digital Twins in Catena-X](https://catenax-ev.github.io/docs/next/standards/CX-0002-DigitalTwinsInCatenaX)
- [ ] [CX-0018 Data Space Connectivity (EDC)](https://catenax-ev.github.io/docs/next/standards/CX-0018-DataspaceConnectivity)
- [ ] [CX-0126 Industry Core: Part Type 2.0.0](https://catenax-ev.github.io/docs/standards/CX-0126-IndustryCorePartType)
- [ ] [CX-0127 Industry Core: Part Instance 2.0.0](https://catenax-ev.github.io/docs/standards/CX-0127-IndustryCorePartInstance)
- **Data Format:**
- [ ] The data model is based on a [published Semantic Model](https://github.com/eclipse-tractusx/sldt-semantic-models)
- [ ] The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the [overarching architecture](https://eclipse-tractusx.github.io/docs/tutorials/e2e/inform/architecture)
- [ ] Potential risks or conflicts with existing architecture has been assessed

**Justification:** _(Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)_

## Additional information

- [ ] I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)