feat: Add text support for ogre 2

[jmachowinski]

🎉 New feature

Closes #1264

Summary

Fully vibe coded port of the ogre 1 text support.

Backport Policy

• This is safe to backport to the following versions:
  • Jetty
  • Ionic
  • Harmonic
  • Fortress
• This should not be backported
• I am not sure
• Other (fill in yourself)

Test it

You will need some plugin etc to test and verify this.
The text_TEST more or less only test if it is not crashing,
but not the actual rendering.

Checklist

• Signed all commits for DCO
• Added a screen capture or video to the PR description that demonstrates the feature
• Added tests
• Added example and/or tutorial
• Updated documentation (as needed)
• Updated migration guide (as needed)
• Consider updating Python bindings (if the library has them)
• codecheck passed (See contributing)
• All tests passed (See test coverage)
• Updated Bazel files (if adding new files). Created an issue otherwise.
• While waiting for a review on your PR, please help review another open pull request to support the maintainers
• Was GenAI used to generate this PR? If so, make sure to add "Generated-by" to your commits. (See this policy for more info.)

Generated-by: GLM-5.2 SWE-1.6 Claude Opus 4.8

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by and Generated-by messages.

Backports: If this is a backport, please use Rebase and Merge instead.

[jmachowinski]

The tests on homebrew are failing as USE_OGRE2_OVERLAY is disabled.

What is the best approach here, should I guard that test with an ifdef ?

[jmachowinski]

I found some crashes if toggling visibility, setting to draft for now

[jmachowinski]

The crash I was seeing was due to the need to remove geometries explicitly and not only the visual the geometry was attached to.

E.g. :

      // Without this line you will get a crash
      label.visual->RemoveGeometries();
      scene->RootVisual()->RemoveChild(label.visual);
      label.visual.reset();
    }

@iche033 Is this expected behavior or rather a bug in the visual ?