Fix paired stereo review in the web interface

[mattdawkins]

Web review can load an individual stereo camera as a standalone dataset, showing one side per entry. The web dataset picker also excluded multicamera parents because it reused scoring restrictions.

Resolve camera-folder selections and camera viewer links to the stereo parent before loading review. Selecting either camera, both cameras, or the parent now loads one sequence with paired views for matching track IDs. Review-specific listing and picker hooks allow whole rigs. Internal camera IDs remain separate for media, annotations, and saves.

Load the parent hierarchy and shared type styles for camera review configs, and honor cameraOrder without dropping cameras from incomplete legacy lists. Both platforms use the shared review controls for synchronized frames and zoom/pan, linked classification/acceptance/deletion, and camera-specific geometry edits.

Validation:

• 202 tests passed across web-girder and shared review services, components, and helpers.
• Regression cases include starting from either raw camera folder or composite camera link, duplicate parent/camera selections, deferred loading, standalone datasets, sparse frames, hierarchy-aware edits, camera-specific saves, retry, and denied camera access.
• ESLint and TypeScript checks passed.
• Web production build passed; desktop production build passed during the initial PR validation.

No live deployed stereo dataset was available for a browser walkthrough. Integration tests use real web adapters with mocked Girder responses and media decoding.

[BryonLewis]

Tested and allows adding multicamera datasets for review on web. Added a small change to prevent sub-cameras from being added as their own dataset.