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/interaction-manager.test.ts

@@ -23,7 +23,9 @@ describe('InteractionManager', () => {
     const manager = new InteractionManager(api);
 
     manager.initialize();
-    expect(api.getConditionsManager().setState).toBeCalledWith({ interaction: false });
+    expect(api.getConditionStateManager().setState).toBeCalledWith({
+      interaction: false,
+    });
     expect(element.getAttribute('interaction')).toBeNull();
   });
 
@@ -62,11 +64,11 @@ describe('InteractionManager', () => {
     vi.useFakeTimers();
     vi.setSystemTime(start);
 
-    expect(api.getConditionsManager().setState).not.toBeCalled();
+    expect(api.getConditionStateManager().setState).not.toBeCalled();
 
     manager.reportInteraction();
 
-    expect(api.getConditionsManager().setState).toHaveBeenLastCalledWith(
+    expect(api.getConditionStateManager().setState).toHaveBeenLastCalledWith(
       expect.objectContaining({
         interaction: true,
       }),
@@ -77,7 +79,7 @@ describe('InteractionManager', () => {
     vi.setSystemTime(add(start, { seconds: 10 }));
     vi.runOnlyPendingTimers();
 
-    expect(api.getConditionsManager().setState).toHaveBeenLastCalledWith(
+    expect(api.getConditionStateManager().setState).toHaveBeenLastCalledWith(
       expect.objectContaining({
         interaction: false,
       }),