[BUG] missing import statements when adding a jsx element inside a nested editor

• I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
• I have read the documentation and cannot find an answer.

Describe the bug
When a jsx component is added from inside a nested lexical editor, the import statement is ignored. The issue comes from the NestedLexicalEditor which prevents adding import statements when calling exportLexicalTreeToMdast with addImportStatements=false. It makes sense to not import directly inside the nested editor, but the import statement on the primary root seems not to be added.

Reproduction
See PR #734 where this issue is mentioned. The user story story=jsx--import-statements-nested can be used to reproduce the issue by focusing the admonition content and then clicking inside the toolbar Zazz. The inserted component does not trigger an import statement. Is this enough or do you need an explicit repro? :)

Start with NestedLexicalEditor and the exportLexicalTreeToMdast call described in the issue. Reproduce using story=jsx--import-statements-nested: focus the admonition content and click Zazz in the toolbar. Done means the inserted JSX component causes the primary root editor to include its import statement while nested export still avoids adding imports locally.