feat: allow correcting honey measurements and queen evaluations

Both records could be created but never changed. A water-content reading
decides whether a batch may be sold as honey at all, and queen ratings drive
breeding decisions - a slipped digit in either is exactly the kind of wrong
value that must not be left standing.

- New PATCH /honey-batches/measurements/:measurementId behind
  honey-batches:measure, and PATCH /queens/evaluations/:evaluationId behind
  queens:evaluate. Both are addressed by the child record's own id, so the
  routes take two path segments and do not collide with PATCH /:id.
- Both log before and after data, like every other correction.
- The measurement list on the honey batch page and the rating list on the queen
  page gained an edit dialog; the rating dialog reuses the existing criteria
  list rather than restating it.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

ApiCore-Frontend/src/lib/queens/api.ts

@@ -2,6 +2,7 @@ import { apiFetch } from "@/lib/auth/api-client";
 import {
   AssignColonyInput,
   CreateQueenEvaluationInput,
+  UpdateQueenEvaluationInput,
   CreateQueenInput,
   Queen,
   QueenColonyHistoryEntry,
@@ -59,6 +60,16 @@ export function fetchQueenEvaluations(id: string): Promise<QueenEvaluation[]> {
   return apiFetch<QueenEvaluation[]>(`/queens/${id}/evaluations`);
 }
 
+export function updateQueenEvaluation(
+  evaluationId: string,
+  input: UpdateQueenEvaluationInput,
+): Promise<QueenEvaluation> {
+  return apiFetch<QueenEvaluation>(`/queens/evaluations/${evaluationId}`, {
+    method: "PATCH",
+    body: JSON.stringify(input),
+  });
+}
+
 export function addQueenEvaluation(
   id: string,
   input: CreateQueenEvaluationInput,