[CONCEPT] Provide more details on policies when publishing assets

As a user , I want to have a good uux experience , so that the app is convenient to use .

Hints / Details

from julias feedback: https://github.com/eclipse-tractusx/sig-release/issues/506#issuecomment-1944683605

Make sure policies are detailed enough at selection, so user knows exactly which policy he chooses.
Location for managing policies will be provided when policy management in FE is implemented

current backend policy response

[ { "policyId": "default-policy", "createdOn": "2024-04-12T04:04:34Z", "validUntil": "2029-04-12T04:04:34Z", "permissions": [ { "action": "USE", "constraints": { "and": [ { "leftOperand": "PURPOSE", "operatorTypeResponse": "EQ", "rightOperand": "ID 3.0 Trace" }, { "leftOperand": "PURPOSE", "operatorTypeResponse": "EQ", "rightOperand": "ID 3.1 Trace" }, { "leftOperand": "PURPOSE", "operatorTypeResponse": "EQ", "rightOperand": "R2_Traceability" }, { "leftOperand": "FrameworkAgreement.traceability", "operatorTypeResponse": "EQ", "rightOperand": "active" }, { "leftOperand": "Membership", "operatorTypeResponse": "EQ", "rightOperand": "active" } ], "or": [ { "leftOperand": "PURPOSE", "operatorTypeResponse": "EQ", "rightOperand": "ID 3.0 Trace" }, { "leftOperand": "PURPOSE", "operatorTypeResponse": "EQ", "rightOperand": "ID 3.1 Trace" }, { "leftOperand": "PURPOSE", "operatorTypeResponse": "EQ", "rightOperand": "R2_Traceability" }, { "leftOperand": "FrameworkAgreement.traceability", "operatorTypeResponse": "EQ", "rightOperand": "active" }, { "leftOperand": "Membership", "operatorTypeResponse": "EQ", "rightOperand": "active" } ] } } ] } ]

Acceptance Criteria

provide a concept
- how policy details can be provided when publishing assets
- How can there be a differentiation between usage and access policies?
- usage policy maybe as a separate dropdown
Create a Implementation issue based on this concept

eclipse-tractusx / traceability-foss