move configuration pages to guides

Author: s1gr1d

docs/platforms/javascript/common/configuration/micro-frontend-support.mdx renamed to docs/platforms/javascript/common/guides/micro-frontends.mdx

@@ -1,5 +1,5 @@
 ---
-title: Micro Frontend Support
+title: Micro Frontends
 sidebar_order: 200
 description: Learn how to identify the source of errors and route events to different Sentry projects when using micro frontend or module federation.
 keywords:
@@ -14,7 +14,7 @@ keywords:
 If your frontend includes JavaScript bundles from multiple sources with
 different release cycles, you may want to identify these or route events to specific projects. This is especially useful if you've set up [module federation](https://module-federation.github.io/) or a similar frontend architecture.
 
-Below we offer two approaches. 
+Below we offer two approaches.
 
 <Note>
 In all cases `Sentry.init()` must never be called more than once, doing so will result in undefined behavior.
@@ -60,7 +60,7 @@ module.exports = {
 };
 ```
 
-Once metadata has been injected into modules, the `moduleMetadataIntegration` 
+Once metadata has been injected into modules, the `moduleMetadataIntegration`
 can be used to look up that metadata and attach it to stack frames with
 matching file names. This metadata is then available in the `beforeSend` callback
 as the `module_metadata` property on each `StackFrame`. This can be used to identify