docs: include info about cross-loading esm and non esm (module-federation#3264)

Author: ScriptedAlchemy

apps/website-new/docs/en/guide/basic/runtime.mdx

@@ -46,6 +46,12 @@ init({
       entry: "http://localhost:3006/remoteEntry.js",
       alias: "app2"
     },
+{
+      name: "@demo/app4",
+      entry: "http://localhost:3006/remoteEntry.mjs",
+      alias: "app2",
+      type: 'module' // tell federation its a certain format, like ESM module
+    },
   ],
 });
 

apps/website-new/docs/en/guide/troubleshooting/runtime/RUNTIME-001.mdx

@@ -13,6 +13,7 @@ However, during this loading process, registered producers are inaccessible. The
 1. The remoteEntryUrl is not right.
 2. The remoteEntry file does not mount the container correctly.
 3. Network problem, the resource cannot be accessed.
+4. The remote type is a different format and not specified in either the plugin or in the `init` for the remotes details.
 
 ## Solutions
 
@@ -22,3 +23,5 @@ There are corresponding solutions for the reasons:
   - If using manifest, check the publicPath and remoteEntry.name  fields in the manifest
 2. If the project builder is rspack, check whether [runtimeChunk](https://rspack.dev/config/optimization#optimizationruntimechunk) is set in the final build configuration. If so, delete this configuration.
 3. Check if the resource is externally accessible.
+4. Loading a ESM remote from a non-esm host
+  -  setting `type: 'module'` on the remote config