Merge node with javascript platform (#9710)

* Merge node with javascript platform
* Create symlinks for all previous node guides
* Fix platform icons
* Add categories to all SDKs, remove duplicate configuration where possible
* Set SDK names; change titles of Profiling pages
* Add redirects

Author: stephanie-anderson

docs/contributing/pages/components.mdx

@@ -121,7 +121,7 @@ If content is specified, it will automatically hide the content when the given `
 </Note>
 
 ```markdown {tabTitle:Example}
-<ConfigKey name="send-default-pii" notSupported={["javascript", "node"]}>
+<ConfigKey name="send-default-pii" notSupported={["javascript"]}>
 
 Description of send-default-pii
 
@@ -229,7 +229,7 @@ This will direct users to a page where they can choose the platform, and then to
 Render a section based on the currently selected `platform` in context. When the platform is not valid, the content will be hidden.
 
 ```markdown {tabTitle:Example}
-<PlatformSection notSupported={["javascript", "node"]}>
+<PlatformSection notSupported={["javascript"]}>
 
 Something that applies to all platforms, but not javascript or node.
 

docs/platforms/javascript/common/best-practices/browser-extensions.mdx

@@ -2,6 +2,14 @@
 title: Browser Extensions
 sidebar_order: 50
 description: Learn how to use Sentry in shared environments (for example in browser extensions or VSCode extensions).
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 keywords:
   [
     "BrowserClient",

docs/platforms/javascript/common/best-practices/index.mdx

@@ -2,6 +2,14 @@
 title: Best Practices
 description: "Learn how to set up Sentry in specific scenarios with those best practice guides"
 sidebar_order: 3
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 <PageGrid />

docs/platforms/javascript/common/best-practices/micro-frontends.mdx

@@ -2,6 +2,14 @@
 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.
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 keywords:
   [
     "micro frontend",

docs/platforms/javascript/common/best-practices/multiple-sentry-instances.mdx

@@ -2,6 +2,14 @@
 title: Multiple Sentry Instances
 sidebar_order: 300
 description: Learn how to manage several Sentry instances by creating your own clients.
+notSupported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 keywords:
   [
     "multiple instances",
@@ -110,5 +118,3 @@ scope1.setTag("a", "b");
 scope2.captureMessage("x");
 scope2.setTag("c", "d");
 ```
-
-

docs/platforms/javascript/common/best-practices/offline-caching.mdx

@@ -7,6 +7,13 @@ notSupported:
   - javascript.cordova
   - javascript.electron
   - javascript.wasm
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 If your JavaScript application is designed to continue working offline,

docs/platforms/javascript/common/best-practices/web-workers.mdx

@@ -15,6 +15,13 @@ notSupported:
   - javascript.react
   - javascript.vue
   - javascript.wasm
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 Sentry's Browser SDK supports [Web Workers API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API). To capture unhandled errors from Web Workers:

docs/platforms/node/common/configuration/application-not-responding.mdx renamed to docs/platforms/javascript/common/configuration/application-not-responding.mdx

@@ -2,6 +2,14 @@
 title: Application Not Responding (ANR)
 sidebar_order: 70
 description: "Learn how to turn off or specify ANRs for Node.js"
+supported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 keywords:
   [
     "anr",

docs/platforms/node/common/configuration/async-context.mdx renamed to docs/platforms/javascript/common/configuration/async-context.mdx

@@ -2,6 +2,14 @@
 title: Async Context
 sidebar_order: 80
 description: "Learn more about how to isolate Sentry scope and breadcrumbs across requests."
+supported:
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.gcp-functions
+  - javascript.koa
 ---
 
 You can use the `runWithAsyncContext` method to isolate Sentry scope and breadcrumbs to a single request if you are using SDK v7.48.0 or higher. This is useful if you are finding that breadcrumbs and scope are leaking across requests.

docs/platforms/javascript/common/configuration/filtering.mdx

@@ -6,8 +6,7 @@ description: "Learn more about how to configure your SDK to filter events report
 
 When you add Sentry to your app, you get a lot of valuable information about errors and performance. And lots of information is good -- as long as it's the right information, at a reasonable volume.
 
-
-Sentry offers [Inbound Filters](/product/data-management-settings/filtering/) that you can enable per project to filter out various events in sentry.io. You can use our pre-defined inbound filters (e.g. filtering known browser extensions), as well as add your own message-based filters. 
+Sentry offers [Inbound Filters](/product/data-management-settings/filtering/) that you can enable per project to filter out various events in sentry.io. You can use our pre-defined inbound filters (e.g. filtering known browser extensions), as well as add your own message-based filters.
 
 However, we recommend filtering at the client-level, because it removes the overhead of sending events you don't actually want. The Sentry SDKs have several configuration options, which are described in this document, to help you filter out events. To learn more about the event fields you can use for filtering, see [Event Payloads](https://develop.sentry.dev/sdk/event-payloads/).