fix(links): offer the whole vault when linking a document to a record

The visit and vaccination forms asked the document list for a page of
200 while the route accepts at most 100. The refusal read as an empty
list, so the picker said "No documents yet." to anyone with a full
vault, and the only way a scan reached a dose was the seven-day
suggestion offered at upload. The visit form's condition picker had the
same problem against the episode list.

The document pickers now walk the vault page by page at the route's own
limit, so any document can be linked from a vaccination or a visit, and
one document can sit on as many records as it covers. Documents dated
within seven days of the record stay on top under their own heading,
the rest follow by month and are searchable. A failed read now shows an
error with a retry instead of passing for an empty list.

Refs #1024, #1005

src/lib/query-keys/documents.ts

@@ -54,6 +54,13 @@ export const documentKeys = {
    */
   inboundDocumentPicker: (q: string) =>
     ["documents", "inbound", "picker", q] as const,
+  /**
+   * The whole vault as a link-picker option list (every page, walked at the
+   * list route's ceiling), shared by the visit and vaccination forms. Own
+   * segment because the shape is a flat document array, not a page.
+   */
+  inboundDocumentVaultPicker: () =>
+    ["documents", "inbound", "vault-picker"] as const,
   /**
    * Storage usage + effective limits (`GET /api/documents/inbound/usage`).
    * Invalidated through the `["documents"]` prefix after every upload /