ci(hypatia): standardise the wrapper caller id to the canonical hypatia (#11)

The check a reusable-caller job publishes is `<caller job id> / <inner
job display name>`. The estate's canonical required context is `hypatia
/ Hypatia Neurosymbolic Analysis`
(`docs/audits/audit-hypatia-pin-orphan-2026-05-27.adoc`), so the caller
job must be named `hypatia`. This wrapper named it `scan`, and so
published `scan / Hypatia Neurosymbolic Analysis` — two names for one
gate, and any requirement written against one is unsatisfiable in a
repository that publishes the other (the defect class of
hyperpolymath/tropical-types#17).

**Rename only** — the job body, its pin, its inputs and its secrets are
byte-for-byte unchanged.

Audit-first, requirement-aware: this is `--fix` output from
`scripts/propagate-hypatia-caller-id.sh` in `hyperpolymath/standards`
(the script stages; it never commits or pushes). The repository's active
branch rulesets were read before the rename — **no rule here names the
old prefixed context**, so the published name and every requirement stay
in agreement.

Author: hyperpolymath

.github/workflows/hypatia-scan.yml

@@ -27,5 +27,5 @@ permissions:
   security-events: write
 
 jobs:
-  scan:
+  hypatia:
     uses: hyperpolymath/standards/.github/workflows/hypatia-scan-reusable.yml@d5fe075a50ab3ce4f41614d66ed77f152fda134f