Fix false positive i18n warnings for translated glossary term references

[m-aciek]

Purpose

Fix false positive translation warnings introduced by the reference comparison in #14001, following the adjustments in #14144 and #14172.

Translators should be able to translate hyperlink display text and glossary term names without receiving an “inconsistent references” warning when the references still identify the same targets.

For example, translating :term:`text encoding` to :term:`kodowanie tekstu` should be accepted when both names identify the same glossary entry. Changing the reference to a different glossary entry should still warn.

This addresses the remaining cases in #14162.

Changes

• Compare named hyperlinks by their target IDs after applying the existing reference-name repair. Translated display text and unambiguous translated names are accepted; ambiguous assignments still warn.
• Compare glossary references by the glossary entries they identify, allowing translated term names and case-insensitive lookup.
• Defer comparisons involving glossary terms until all documents have been read and their translated terms registered. These checks also work for included documents in singlehtml and LaTeX builds.
• Preserve checks for changed targets, roles, domains, and reference multiplicity. Reference ordering remains unrestricted, and # noqa remains supported.

Validation

Regression coverage includes translated display text and names, embedded newlines in term targets, reordered references, incorrect target changes, missing or duplicated references, ambiguous named links, and # noqa.

Tests also cover glossaries in other documents, parallel reading, singlehtml and LaTeX document assembly, and rebuilds using saved doctrees.

Local validation: 157 tests passed across the i18n, transforms, and standard-domain suites with Python warnings treated as errors. Ruff, mypy, Pyright, and ty passed for the changed Python files.

Developed with assistance from Copilot and Codex; reviewed and tested.

References

Closes #14162.

[m-aciek]

ty failures should be addressed by #14296.

[m-aciek]

I wonder if revert of #14001 wouldn't be a better alternative. I need yet to sit down to it.

[m-aciek]

After looking into this further, I think keeping the checks and fixing the false positives is preferable. Reverting #14001 would also remove useful warnings about incorrect references, including target substitutions that preserve the number of references.

The updated implementation accepts translated display text and glossary names when they identify the same targets, while retaining warnings for actual inconsistencies. It also preserves the citation and footnote checks. This addresses the false positives without losing those diagnostics.

The PR description is updated and reflects current state.

[m-aciek]

No failures attributable to this PR's changes on head 2af4896f6, compared with base e44a40eb2.

CI failures	Cause and verification
15 jobs: the same six tests fail	Pygments 2.21.0 changes HTML quote escaping. All six fail on both the base and PR head; all pass with Pygments 2.19.2.
LaTeX: 51 failures	Existing incompatibilities with Docutils's development version, plus those Pygments failures. Reproduced on the base.
Docutils HEAD: 53 failures	Reproduced 52 on both revisions using CI's exact Docutils commit, 335c924f838ac9180231cf2164f301cc6f6b4ca1. The remaining Python-domain assertion passes locally on both, so its cause remains unconfirmed.

The Docutils failures include string/integer mismatches in writers, changed doctest behavior, and missing output files after earlier build failures. See the CI run.

All 41 tests added by this PR pass in the standard and Docutils HEAD jobs. Ruff, mypy, Pyright, ty, and documentation checks also pass. See the lint run.