feat(library): add focused photo review mode

[zjywill]

Description

Adds a focused Photo Review mode to the library for fast, one-photo-at-a-time culling and inspection without entering the editor or hiding the existing RapidRAW shell.

This is intentionally narrower than a full preview/loupe workspace. It reuses RapidRAW's existing preview generation, ratings, metadata, file actions, and native Cull view instead of adding another rendering pipeline or cache layer.

Type of Change

• Bug fix
• New feature
• Breaking change
• Performance improvement
• Code refactoring
• Documentation update
• UI/UX improvement
• Build/CI or Dependency update

Changes Made

• Adds Photo Review alongside the existing Grid, List, and Cull library modes.
• Keeps the title bar and folder panel visible so review stays within the normal library layout.
• Adds continuous zoom in/out, fit/actual-size reset, panning, and preview prefetching.
• Supports keyboard navigation, star ratings, Pick/Reject/Clear flags, optional auto-advance, filters, and a toggleable filmstrip.
• Sends up to six selected photos into RapidRAW's native Cull view, matching the current upstream comparison limit.
• Provides an archive workflow for rejected originals and sidecars, including restore and system-Trash cleanup actions.
• Hides internal culling flag tags from normal user tag menus.
• Adds synchronized strings for all 12 locale files.

Screenshots/Videos

Photo Review keeps the title bar and folder panel visible while exposing filters, filmstrip navigation, culling actions, and zoom controls.

Testing

• I have tested these changes locally and confirmed that they work as expected without issues

Commands run:

• npm ci
• npm run i18n:check
• npm run build
• Prettier across all files changed by this PR
• ESLint for the new Photo Review component, hooks, and utilities
• Manual Tauri review-flow verification on macOS

Test Configuration:

• OS: macOS 26.5.2
• Hardware: Apple M4 Mac mini, 24 GB RAM

Checklist

• My code follows the project's code style
• I haven't added unnecessary AI-generated code comments
• My changes generate no new warnings or errors

Additional Notes

• Based on upstream main at 2a40a4b7.
• App icon, title-bar behavior, and the internal culling plan are deliberately excluded from this PR.
• Related to the focused review/culling portions of FEATURE: Library View to have Large Preview Pane for comparing multi selected images for culling #881, FEATURE: Improve Culling Support #1057, and FEATURE: Library-First / Advanced Viewer Workspace #1382.
• Upstream main currently has a pre-existing cargo fmt failure in src-tauri/src/exif_processing.rs (run 29759193582); that file is not changed here.

AI Disclaimer:

Please state the involvement of AI in this PR:

• This PR is entirely AI-generated
• This PR is AI-generated but guided by a human
• This PR was handwritten with AI assistance (spell check, logic suggestions, error resolving)
• This PR contains only blood, sweat, and coffee (AI-free)

[erik-nie]

please also add the shooting data to culling (ISO, A, T, focal-point, focal-length). perhaps optional.
I shoot several images with different settings, good to see them while culling.
Thanks! I much appreciate this.
It would also be great if there is an option to delete the skipped images, or make a delete option.

[zjywill]

Thanks @erik-nie. I added these follow-ups in 0d02d900:

• Photo Review now has an optional, persisted shooting-info overlay for shutter speed, aperture, ISO, and focal length. The values update immediately while navigating, without per-photo animation.
• Archive Rejects remains the primary safe workflow. A secondary action can move rejected photos and their sidecars to the system Trash after an explicit confirmation; Cancel receives initial focus, and the native command never falls back to permanent deletion.
• Empty Archive now uses the same no-permanent-delete Trash path.

I have not labeled SubjectDistance as a focal/AF point: RapidRAW's normalized EXIF data does not currently expose a reliable cross-vendor AF-point field. That should be handled separately once the metadata mapping is defined rather than showing misleading data.

Validated with cargo check --lib, the focused Rust test harness, the production frontend build, i18n checks across 12 locales, focused ESLint, formatter checks, and a manual macOS Tauri review.

[zjywill]