Refactor state management

[ShrimpCryptid]

Use Case

State is currently a loose collection of useStates in the main app viewer, and it's gotten large enough that passing props around is becoming a chore (see CanvasWrapper). This would be a great opportunity to switch a state management framework (e.g. Zustand, Redux).

                <CanvasWrapper
                  loading={isDatasetLoading}
                  loadingProgress={datasetLoadProgress}
                  canv={canv}
                  collection={collection || null}
                  vectorData={motionDeltas}
                  dataset={dataset}
                  datasetKey={datasetKey}
                  featureKey={featureKey}
                  selectedBackdropKey={selectedBackdropKey}
                  colorRamp={getColorMap(colorRampData, colorRampKey, colorRampReversed)}
                  colorRampMin={colorRampMin}
                  colorRampMax={colorRampMax}
                  isRecording={isRecording}
                  categoricalColors={categoricalPalette}
                  selectedTrack={selectedTrack}
                  config={config}
                  updateConfig={updateConfig}
                  onTrackClicked={onTrackClicked}
                  inRangeLUT={inRangeLUT}
                  onMouseHover={(id: number): void => {
                    const isObject = id !== BACKGROUND_ID;
                    setShowObjectHoverInfo(isObject);
                    if (isObject) {
                      setLastValidHoveredId(id);
                    }
                  }}
                  onMouseLeave={() => setShowObjectHoverInfo(false)}
                  showAlert={isInitialDatasetLoaded ? showAlert : undefined}
                />

Acceptance Criteria

• Move all useState declarations in Viewer.tsx into their own hook or store.
• Move shared state modifiers (like setFrameAndRender, findTrack, handleDatasetChange, replaceDataset) into hook or store.
• Remove prop drilling for CanvasWrapper.tsx, Export.tsx, CanvasHoverTooltip, ColorRampDropdown, and any other components with more than 8 props in Viewer.tsx.

Details

• This will likely need to be split up into multiple PRs.