Visualizer Refactor

[RoboDoig]

This PR refactors the dynamic foraging visualizers to use a full Bonsai ImGui approach according the the requirements outlined in the visualizer refactor milestone

Addresses issues #99, #100, #101, #102, #103, #104, #105.

Individual visualizers take as input an observable source that describes their parent layout group (e.g. tab area, table window) such that visualizers can be reorganised within a parent layout structure. Generally, data is mapped to visualizers by externalized subject names corresponding to the appropriate data source or event.

[RoboDoig]

@bruno-f-cruz @micahwoodard - for rotating the image in shader, is free rotation necessary or is it always done in 90 degree increments? Both possible just much more straightforward for 90 degree increments!

[micahwoodard]

I get crashing and memory errors without this take until which is why I added originally.

Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at OpenTK.Graphics.OpenGL4.GL.DeleteTextures(Int32 n, Int32& textures) in I:\work\github\opentk\src\OpenTK\Graphics\OpenGL4\GL4.cs:line 16159

[micahwoodard]

@RoboDoig I added back the takeuntil to circumvent the AccessViolationException to be able to continue running a mouse for testing today. We can remove and fix with something else though

[micahwoodard]

@bruno-f-cruz @micahwoodard - for rotating the image in shader, is free rotation necessary or is it always done in 90 degree increments? Both possible just much more straightforward for 90 degree increments!

Oh sorry I missed this. 90 degree increments

[micahwoodard]

@RoboDoig @bruno-f-cruz do we want to just merge this? This branch is what we've been using during testing and what I've been merging fixes into. Just seems like this pr has gotten big and hard to track everything that's going on

[RoboDoig]

@micahwoodard yes agreed that it's gotten hard to track, I believe on my end what is still outstanding is dynamically creating the camera visualizers from the cameras specified in the settings, as opposed to them being hard coded on the visualizer. Is there anything else?

[micahwoodard]

@RoboDoig I think there a couple of smaller issues like #173, #179, and #111 but ones I think we can address after merging in separate pr's. I would also be fine merging this pr as is and having a separate pr for the dynamic camera visualizers

[micahwoodard]

We ran two session yesterday with latest changes here so I feel okay about merging unless @RoboDoig or @bruno-f-cruz disagree