Fix types by moving some dev-dependencies to dependencies

[remcohaszing]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)
• If applicable, I’ve added docs and tests

Description of changes

mdast-util-mdxjs-esm depends on the types of both mdast-util-from-markdown and mdast-util-to-markdown.

[ChristianMurphy]

Interesting 🤔
👍 for ensuring all the types are in place.
@wooorm thoughts on whether those types make sense coming from mdast-util=* packages or if they should live in @types/mdast or somewhere else?

[remcohaszing]

FYI this is one of the type issues I ran into when upgrading xdm.

[wooorm]

@ChristianMurphy I think these types:

mdast-util-mdxjs-esm/index.js

Lines 2 to 5 in 899df97

	* @typedef {import('mdast-util-from-markdown').Extension} FromMarkdownExtension
	* @typedef {import('mdast-util-from-markdown').Handle} FromMarkdownHandle
	* @typedef {import('mdast-util-to-markdown').Options} ToMarkdownExtension
	* @typedef {import('mdast-util-to-markdown').Handle} ToMarkdownHandle

make more sense in their respective utilities, rather than adding them to @types/mdast, which I feel is more about node interfaces