Fix nested tab indentation in response templates (pymdownx regression)

After issue #35 introduced a response-code tab wrapper (=== "200 OK"),
content-type tabs became doubly nested. The `{% include
"partial/content-examples.html" %}` directive inside the 8-space
content-type tab context rendered at column 0, breaking the indentation
chain so that subsequent `??? hint` admonition blocks were not
recognised as belonging to the tab content.

Fix: inline the content-examples rendering directly in
request-responses.html with proper 8-space indentation so all content
(code blocks, warnings, admonitions) sits correctly inside the nested
tab structure.

Regenerated snapshots for example1–example4-split.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: RobertoPrevato

openapidocs/mk/v3/views_mkdocs/partial/request-responses.html

@@ -9,7 +9,14 @@
     {%- with content = handler.simplify_content(definition.content) %}
     {% for content_type, definition in content.items() %}
     === "{{content_type}}"
-        {% include "partial/content-examples.html" %}
+        {% for example in handler.get_content_examples(definition) %}
+        {% if example.value %}
+        ```json
+        {{handler.write_content_example(example, content_type) | indent(8) | safe}}
+        ```
+        {% if example.auto_generated %}<span class="small-note">⚠️</span>&nbsp;<em class="small-note warning">{{texts.auto_generated_example_note}}</em>{% endif -%}
+        {% endif %}
+        {% endfor %}
         {% if "alt_types" in definition %}<em class="small-note alt-types">{{texts.other_possible_types}}: {{definition.alt_types | join(", ")}}</em>{% endif %}
 
         ??? hint "{{texts.schema_of_the_response_body}}"