Remove LogicalConstraint from Usage Policy Example

[matgnt]

As discussed in our meeting last week, I think we should remove the LogicalConstraint -> and from the Usage Policy example. This is not required since we crurrently don't want to have, the other possible LogicalConstraints like or, xone, andSequence as defined here: https://www.w3.org/TR/odrl-model/#constraint-logical

tractusx-profiles/cx/policy/specs/policy.definitions.md

Line 290 in 64f83dd

"and": [

with

"constraint": {
        "and": [
             {
              "leftOperand": "cx-policy:FrameworkAgreement",
              "operator": "eq",
              "rightOperand": "traceability:v1.0"
            },
            ...
         ]
      }

without

"constraint": [
             {
              "leftOperand": "cx-policy:FrameworkAgreement",
              "operator": "eq",
              "rightOperand": "traceability:v1.0"
            },
            ...
        ]

Both are valid ODRL and both have the same meaning. Since we don't want to support the other LogicalConstraints, it is easier to understand to just remove the additional layer.
@jimmarino can you please have a look?
Thanks,
Matthias

[matgnt]

closing this as discussed in eclipse-tractusx/tractusx-edc#856 (comment)
It is important what is desired in tx-edc.
ODRL may allow this, but we'll not explain this and use it in Cx as it seems.