BG - Removing a Grabbable component should not auto-remove other components

[j-conrad]

Description
When adding a Grabbable component to an object, the Rigidbody and Physics Shape components get added automatically.
This is generally a good and helpful thing.
However, when removing the Grabbable component, it also automatically removes Rigidbody and Physics Shape which is often undesired.
It is common to want to remove the Grabbable component yet keep the rest of the components intact.

To Reproduce
Steps to reproduce the behavior:

1. Add a Rigidbody and Physics Shape components to a cube.
2. Add a Grabbable component to the cube.
3. Remove the Grabbable component
4. The Rigidbody and Physics Shape components get removed as well.

Expected behavior
Removing a Grabbable component should leave other components alone.

Hardware

• Device: Desktop
• OS: Windows
• Browser: N/A

[Exairnous]

The current behavior is actually the expected behavior and has to do with how dependencies are managed. The BG RigidBody and BG Physics Shape components are dependencies of the BG Grabbable component and so are added/removed with the BG Grabbable component as one complete package. The same relationship exists between the Waypoint component and the Networked component or the Audio and Audio Params components. So while I understand the want for not removing the other components, this is going to take some design work to allow (assuming we stick mainly to the current dependency paradigm, which I think we should). The first thought that springs to mind is to add a drop down menu to the remove button with an option to ignore dependencies, but then what do you do if someone does that on a Waypoint component and the Networked component gets left behind? Such an option might work better if applied to soft dependencies as mentioned here: Hubs-Foundation/hubs-blender-exporter#247 (comment)