Fix issue with owl:hasValue --> owl:someValueFrom and adapt to multiple restrictions

• New schema defines restrictions e.g. ucums with owl:someValuesFrom and not with owl:hasValue. We check the latter first and if it's empty we extract the former.
• A new pattern allows multiple restrictions on some properties. This was creating a wrong constraint. We now separate the restrictions and loop over them. The cardinality restrictions are currently applied to both cases, i.e. also on the lower level. Maybe we can discuss if it should be applied only to the property that does not have prop_pipeline defined. Example:

Schema:

Shacl: