#77374Opposite MM relation between both new entities not created
Description
Scenario:
- usage in a workspace
- tt_content and sys_category records are created at the same time with defining an MM relation
- sys_category.items (group/db field, with MM and opposite usage defined) is filled with accordant tt_content record
- the remap-stack in DataHandler does not consider references that are defined in a group/db field
- thus, these kind of relations are just not set, since the opposite reference uid cannot be resolved
- process group/db relations with new record uids in remap-stack