Rules: object_id incorrectly refers to non-existent DetectedObject message

[TimmRuppert]

Describe the bug

Some object_id fields use the rule refers_to: DetectedObject, but there is no single DetectedObject message. It seems the intended meaning is likely "the header.tracking_id field within either DetectedStationaryObject or DetectedMovingObject."

Currently, the rule syntax does not support or conditions.

As a result, this creates significant issues when using the new qc-osi-trace if the object_id field is populated.

You can find all occurrences of this rule in the repository.

[pmai]

We probably should extend the rule language to allow expressing DetectedStationaryObject or DetectedMovingObject, e.g. by allowing an array/list of types...