OptionalallWhen a controller legally has MORE THAN ONE relationship of this kind
(e.g. two separate IfcRelAssignsToControl records for the same
schedule), every member across ALL of them — used only to decide which
requested ids are genuinely new, never as the list written back. Writing
this union into relId's own slot would copy a secondary relationship's
members into the primary one, duplicating membership while leaving the
secondary relationship untouched. Defaults to relatedIds when absent
(the single-relationship case, where the two are the same set).
The relationship's current RelatedObjects (or Components), in file order.
OptionalrelatingThe relationship's RelatingObject, when the caller is supplying a nesting graph.
One relationship the caller already found referencing an id, so the builders below never need to scan the store themselves — see the module header.