Too large accumulated bounding box often leads to poor default camera view

[roym899]

Describe the annoyance
A good example is the nuScenes one, where initially some data is logged close to the origin until the first transform for the car is logged; the subsequent data is then far away from the origin, and the accumulated bounding box will be way too big.

The too large bounding box makes double click behave quite unintuitively as it doesn't focus on what's currently in view, but rather resets the view to something pretty useless.

In my experience this is quite a common issue, that sometimes can be worked around by logging data in a specific order. However, that is not a nice solution.

Expected behavior
As discussed with @Wumpf it might be better to always focus on the current bounding box until the user has moved the camera.

Maybe adding an option to the Camera section for the 3D blueprint to allow switching between focusing on the accumulated and the current bounding box might be good to not make things worse in cases where the accumulated bounding box is more useful.

Related to #810.

[roym899]

Maybe worth noting that on repopulating the accumulated bounding box is reset (hence using the current bounding box for the camera view).