Create CI pipeline to validate anchor link functionality in localized content

Current issue is a follow up on this thread: #183 (comment 2621036727)

Goal

Create a focused CI test that validates anchor link functionality specifically for localized content.

This automated CI validation need to ensure that Japanese URLs correctly use English anchor IDs, anchor links within localized pages function properly (see related #292 (closed)), cross-references between localized files work properly.

The validation should also check for presence of any un-wanted text (JA or not) after the injected anchor link in a JA markdown. See thread here: #333 (comment 2786395188)

Consider integrating existing lychee tooling, per this not from Marcel: #333 (comment 2634860257)

Extend this link checking test to GitLab, Runner, Omnibus, Charts, and Operator projects

This should work with our current "in-between" state where not all files are translated - maybe there is a way to validate existing translated content rather than strive for comprehensive link checking initially

********

Add link checking capabilities to i18n pipelines in GitLab, Runner, Omnibus, Charts, and Operator projects to catch translation-specific link breakage. Each project should follow its existing naming conventions and tooling patterns established for English documentation.

Problem TBD. We haven't spotted issues yet, but that's because we haven't been looking. With ~1 million internal links, maybe it's worth adding CI checks before we run into problems (unquote Lauren from this thread: #183 (comment 2626842668))