Potential inconsistency with CameraInputsManager's add and attachElement functions

Not sure if this would be considered a bug, but there may be some inconsistent behaviour with CameraInputsManager’s add and attachElement functions, depending on the order they are called in.

For example:

// Example 1
CameraInputsManager.add(someInput);
CameraInputsManager.attachElement(someNoPreventDefaultValue);
// This will invoke someInput.attachControl(someNoPreventDefaultValue)

// Example 2
CameraInputsManager.attachElement(someNoPreventDefaultValue);
CameraInputsManager.add(someInput);
// This will invoke someInput.attachControl(), without using someNoPreventDefaultValue or the saved CameraInputsManager.noPreventDefault value

Should the following line in the codebase be using input.attachControl(this.noPreventDefault)?

cc @PolygonalSun