feat: Add glossary links to documentation

[solzlivinglife]

  - Automatically linked 80+ glossary terms
  - Links use relative paths for local dev compatibility
  - Covers argument types, variables, control structures, core concepts
  - Tested locally and in production build
  - All links verified working correctly

[GerwinLaagland]

Hello, hello. Thanks for your work! I took a look with @Snooz82 at the reason why the github actions for this PR is failing.

It turns out that the learning_objectives.md document is used to generate numbers. So it's better to not link any terms when you're working with the LO's themselves.

Example to avoid

Can you remove those? The actions should then work.

[GerwinLaagland]

Hi @solzlivinglife ,

I’d like to correct my earlier comment regarding the GitHub Actions failure — I was mistaken about learning_objectives.md being used to generate numbering. I have misunderstood the explanation that was given to me. Apologies for this, when next @Snooz82 speaks, I should pay better attention. 😰

After reviewing the script responsible for this more carefully, I see that numbering is derived directly from the chapter markdown files under website/docs/chapter-*, and learning_objectives.md is generated from those files.

I'm terribly sorry for the confusion and any extra work this may have caused.

The solution instead is to avoid adding links inside :::Kx[LO-x.x.x] :::-blocks. The LO content is extracted verbatim and reused in generated artifacts (learning_objectives.md and LOs.csv). Including links inside these blocks leads to formatting changes or auto-modifications during the generation step, causes CI to fail if the generated files are altered.

Thanks for your patience — and thanks again for the work on this PR.