Audio and Video components create an unwanted collision box

[j-conrad]

Description
Adding an Audio or Video component to an object auto-generates a collision box at runtime. This collision box often ends up at the scene origin (0, 0, 0) and collides with things unexpectedly.

Screenshots
I'm not sure what collision mask they use, but they collide with objects by default.

If I add a Grabbable component (and maybe other types), the collision will move to the location of the audio or video object.
(Here, I've set the Physics Shape on each to be a little oblong to differentiate them.)
Now, their collision shows up at the object locations:

To Reproduce
Steps to reproduce the behavior:

1. Open the included .blend file
2. Note the objects with audio and video components
3. Export/run in Hubs
4. Turn on debug to see their collision at the origin.

Expected behavior
Audio and Video components should not leave collision lying around.

Hardware

• Device: Desktop
• OS: Windows
• Browser: Chrome

Additional context
If components like these require having some sort of collision, we should consider disabling it whenever possible. Otherwise, we may want to have a separate collision layer for stuff like this.