[1.0] Fix historical pagination and artifact detail lookup

Changing the historical page offset recreates a callback whose effect reloads the first page. Artifact details search only the first 100 list results rather than the existing detail endpoint.

Scope

• Keep loaded history pages when loading older results and reset pagination only for an intentional filter change.
• Fetch artifact details by their ID through the existing authorized detail endpoint.
• Expose failed loads and stale requests without showing results for an old filter/selection.

Acceptance criteria

• Loading multiple older pages retains previous pages without resetting to page one or duplicating results.
• An authorized artifact beyond the first 100 entries can be opened directly; forbidden and missing items remain distinguishable only as permitted.
• Changing filters or selection during an outstanding request cannot overwrite the current view with stale data.

Boundaries

No generic frontend state-management rewrite.

References

• Parent topic: #374.
• Implementation dependencies: #432.
• src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx
• src/flock/frontend/src/components/details/MessageDetailWindow.tsx

Start with src/flock/frontend/src/components/modules/HistoricalArtifactsModule.tsx to trace pagination, filter changes, and request lifecycles, then inspect src/flock/frontend/src/components/details/MessageDetailWindow.tsx for artifact lookup. Verify that older pages remain loaded, authorized details can be opened by ID, failures are exposed, and stale requests cannot replace the current view.