fix(mdxish): callout end tag rendering

[eaglethrost]

	Fix RM-15614

🧰 Changes

As a part to resolve a Callout component deserialization issue in RM-15614, it turns out that particular callout was not creating the correct tree & some its content is incorrectly rendered. The cause was that a logic in the mdxish component transformation which was unwrapping the paragraph from a part of the node that contains the closing tag (if the closing tag is together with the content before it). In the case of the example in the ticket, the Callout ends up with children [h3, text, strong, text] instead of [h3, p]. The inline nodes (text, strong) become direct children of the Callout rather than being nested inside a paragraph element.

The fix is to use the full node content instead of the children only (unwrapped). Did a few testing and I haven't found any regressions, the change should only wrap some content as it originally was which shouldn't cause rendering differences (this is specific to Callouts)

🧬 QA & Testing

Using the content in mdxish:

<Callout theme="info" icon="📘">
### Title here

Body with **markdown** support.
</Callout>

It should render the "Body with markdown support" part in one line

• Broken on production.
• Working in this PR app.

[kevinports]

Lgtm