Implement codegen of doclinks

[emilk]

What

• Closes Doclinks in docstrings in generated code #6848

You can now write doclinks in the docstrings of our .fbs files. Example:

/// See also [archetypes.Image].
table Tensor { … }

The links will be transformed to the appropriate form for the codegen target (Rust doclinks are different from those of Python, C++/doxygen, and website/markdown).

Only links to types are currently supported.

Link checking is not done by the codegen, but the output is checked implicityly by cargo doc, lychee etc.

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I have tested the web demo (if applicable):
  • Using examples from latest main build: rerun.io/viewer
  • Using full set of examples from nightly build: rerun.io/viewer
• The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
• If applicable, add a new check to the release checklist!
• If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

• PR Build Summary
• Recent benchmark results
• Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

[github-actions]

Deployed docs

Commit	Link
4277cb2	https://landing-6z6w63u2x-rerun.vercel.app/docs

[jprochazk]

Does this add speculative-link markers on doclinks for unreleased types?

[emilk]

Does this add speculative-link markers on doclinks for unreleased types?

If the links are relative, maybe I don't have to 😬

[emilk]

To get ?speculative-link to work I need to do some major pluimbing

[emilk]

Ok, ?speculative-links is properly handled now. It required a lot of plumbing.

Probably best to review all this commit-by commit

[jprochazk]

nit: some unfortunate naming: all_objects and objects

[emilk]

yeah, I gave up here