Missing mandatory relationship between a ReviewDecision and a ReviewRequest

[csnyulas]

We are getting a SHACL minimum cardinality violations on the transformation of the can_24_maximal.xml example notice provided for SDK 1.13, because in the generated RDF there is no epo:resolvesReviewRequest relationship between the epo:ReviewDecision and epo:ReviewRequest instances:

This relationship is missing also from the Conceptual Mapping. The most likely reason for it is because the eForms SDK does not provide a field to express this relationship. The following issues were created to clarify the problem: OP-TED/ePO#777 and OP-TED/eForms-SDK#1188