fix(docs): escape example Blade expression in mobile v4 Text doc

[simonhamp]

Summary

The mobile v4 Text edge-component doc page (/docs/mobile/4/edge-components/text) was returning a 500 in production with ErrorException: Undefined variable $variable.

Documentation .md files are rendered through the Blade engine before markdown conversion (ShowDocumentationController::getMarkdownView maps .md → the blade engine). The "Dynamic content" <aside> contained an inline example in prose:

Blade expressions like `{{ $variable }}` work inside text slots.

That {{ $variable }} was neither wrapped in @verbatim nor escaped, so Blade evaluated it as a real variable and threw. (Markdown backticks don't help — Blade runs first. The nearby {{ $score }} example was fine because it lives inside a @verbatim block.)

Fix

Escape the inline expression with @{{ }} — the same convention already used elsewhere in the docs (e.g. super-native/reactivity.md). Blade now emits the literal {{ $variable }}, so the reader still sees the intended text and the page renders.

Tests

tests/Feature/DocumentationRenderingTest.php:

• Regression: GET /docs/mobile/4/edge-components/text returns 200 and shows the literal {{ $variable }}.
• Class-wide guard: renders all 335 docs pages as Blade and asserts none throws — catching any other unescaped example expressions across the docs tree.

Both tests fail on the un-fixed doc (reproducing the exact Undefined variable $variable 500) and pass with the fix. Pint is clean.

Fixes #72