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

@@ -50,7 +50,7 @@ const createTriggerAPI = (options?: {
       },
     }),
   );
-  vi.mocked(api.getConditionsManager().getState).mockReturnValue({});
+  vi.mocked(api.getConditionStateManager().getState).mockReturnValue({});
   vi.mocked(api.getCameraManager).mockReturnValue(createCameraManager());
   vi.mocked(api.getCameraManager().getStore).mockReturnValue(
     createStore([
@@ -319,10 +319,10 @@ describe('TriggersManager', () => {
 
     manager.handleCameraEvent({ cameraID: 'camera_1', type: 'new' });
 
-    expect(api.getConditionsManager().setState).toHaveBeenLastCalledWith({
+    expect(api.getConditionStateManager().setState).toHaveBeenLastCalledWith({
       triggered: new Set(['camera_1']),
     });
-    vi.mocked(api.getConditionsManager().getState).mockReturnValue({
+    vi.mocked(api.getConditionStateManager().getState).mockReturnValue({
       triggered: new Set(['camera_1']),
     });
 
@@ -331,7 +331,7 @@ describe('TriggersManager', () => {
     vi.setSystemTime(add(start, { seconds: 10 }));
     vi.runOnlyPendingTimers();
 
-    expect(api.getConditionsManager().setState).toHaveBeenLastCalledWith({
+    expect(api.getConditionStateManager().setState).toHaveBeenLastCalledWith({
       triggered: undefined,
     });
   });