refactor: Significantly refactor how conditions work internally (#1886)

- Much improved API cleanliness and testability to allow further
extensibility in future
 - Simplified code in `live` view

This technically contains a small change in how overrides work in the
`live` view. Since that change is _closer_ to the documentation, and
since this is likely to be rarely used, this is not considered a
breaking change. Previously, overrides for a given live camera would
always render _as if_ that camera was selected, vs was actually
selected. Now, overrides will only apply in the live view when the
camera is _actually_ selected. If this is an issue for you in practice,
lets discuss.

tests/card-controller/fullscreen/fullscreen-manager.test.ts

@@ -17,7 +17,9 @@ describe('FullscreenManager', () => {
     const manager = new FullscreenManager(api, mock<FullscreenProvider>());
 
     manager.initialize();
-    expect(api.getConditionsManager().setState).toBeCalledWith({ fullscreen: false });
+    expect(api.getConditionStateManager().setState).toBeCalledWith({
+      fullscreen: false,
+    });
   });
 
   it('should correctly determine whether in fullscreen', () => {
@@ -133,7 +135,7 @@ describe('FullscreenManager', () => {
 
       handler();
 
-      expect(api.getConditionsManager().setState).toBeCalledWith({
+      expect(api.getConditionStateManager().setState).toBeCalledWith({
         fullscreen: fullscreen,
       });
     });