On Volume Trigger should take its rotation and scale into account

The on Volume Trigger only uses its extends from the applied rotation and scale. But when when reusing the trigger volumen and rotating or scale it. It comes to wrong results. Depending on the size of the actual volume the difference can be quite severe.

Locate the on Volume Trigger implementation and reproduce the incorrect results with a reused volume that has rotation or scale applied. Trace how the trigger derives its extents, then verify that the result accounts for the volume's rotation and scale and no longer changes incorrectly with its dimensions.

Written by the indexing model from the issue text.