Migrate Matching page to React

[vkirkl]

This is a parent issue for the frontend, backend, and any other supporting work that is necessary to migrate from legacy ia results jsp page[s] and backend dependancies to a new React page that uses new API endpoints.
This iteration of the migration should preserve all existing functionality and introduce no new functionality unless explicitly noted in this issue.

Frontend designs:
Figma design
Notion notes

API requirements notes:

• Frontend needs:
  • Get match candidates
    • need API to fetch match results for a given encounter, supporting:
    • individual-score vs image-score mode
    • algorithm (miewID / Hotspotter / PIE v2, etc)
    • project filter (filter candidates by project)
    • pagination & sorting? not sure if backend if returning all match results
    • Returned info should include:
      • candidate encounter id
      • individual name + id
      • scores per algorithm
      • annotation info: left, top, width, height, rotation, encounterId, etc
      • image width + height
      • image name
      • image rotation info
      • match date
      • inspection result url
  • Confirm match: if we don't want to rewrite merge page (/merge.jsp?individualA=xxx&individualB=xxx) , no new API needed
  • Confirm no match: i think we can reuse {op: "replace/add", path: "individualId"} to assign encounter to a new individual or existing individual
• Object model behind matching API should be sufficiently extensible to handle new matching algorithms - and possibly anticipate "ensembles" of matching algorithms
• Business logic behind matching API should use embeddings / vector db
• Initial "wiring" for PairX / explainability for Miew-id should be added: this is just for dev testing and will not be exposed via UI

[pratisthabuddhacharya]

Since Hotspotter gives a single image, here is the design for Hotspotter Visualization
Also, if we decide to display match criteria in match results page, you can find the designs in here.