Move initialization of navscene navigation mode to future call

For now, we cannot assume that the camera has already been created in initialize - so we must wait until the queue resumes to know that it is there.  This will change once initialize waits for all nodes created inside it to complete before being done
refs #2252
Move initialization of mouse mode to future call

For now, we cannot assume that the camera has already been created in initialize - so we must wait until the queue resumes to know that it is there.  This will change once initialize waits for all nodes created inside it to complete before being done
refs #2252
Have navscene.vwf.yaml automatically disable view-side navigation

refs #2252
Do not set view side navigation mode in sandtable (done in navscene)

refs #2252
Update tutorials to initialize camera properties in a future call

refs #2252
Do not assign backup camera is activeCamera does not yet exist

This was leading to second clients having a prototype camera set as the one they were looking through (which made it unresponsive) - this was first seen in the tutorial apps
refs #2252
Separate disabling of view side nav from setting navscene nav

Disabling the view-side nav only needs to happen once, but setting the navscene nav might happen many times.
refs #2252
Clean up vestigial properties in plane app

refs #2252