Update NodeNorm dev to a current Babel so --labels works out of the box

[gaurav]

NodeNorm dev (https://nodenormalization-sri.renci.org/) reports Babel 2025sep1 from its status
endpoint, while public Babel latest is 2025dec11. xrefs --labels and ids --labels compare
the two and refuse to run on a mismatch, because labels and cliques from one release would not
match cross-references from another:

NodeNorm at https://nodenormalization-sri.renci.org/ was built from Babel 2025sep1, but
https://stars.renci.org/var/babel/latest/ is Babel 2025dec11. Labels and cliques would not match
the cross-references. Point --nodenorm-url at a matching NodeNorm, pin --babel-version to the
release NodeNorm was built from, or pass --allow-version-mismatch to proceed anyway.

So a new user hitting --labels meets a second wall right after #16.

Workarounds today

• BABEL_VERSION=2025sep1 — the Translator outputs tree has a 2025sep1/ release, so pinning it
  makes the versions agree properly rather than suppressing the check. Not available against the
  public tree, which only carries 2025dec11/.
• --allow-version-mismatch — proceeds anyway, and the results are silently cross-release.

Done when

NodeNorm dev's status reports the same Babel release as public latest, and xrefs --labels
runs with no extra flags.