Pre nextjs simplify rust n ruby docs (#8731)

* Remove PlatformSection component from Rust docs
* Remove PlatformSection component from Ruby docs

Author: stephanie-anderson

src/platform-includes/alert-using-a-framework/_default.mdx

@@ -0,0 +1,5 @@
+<Alert level="info" title="Using a framework?">
+
+Get started using a guide listed in the right sidebar.
+
+</Alert>

src/platform-includes/alert-using-a-framework/ruby.delayed_job.mdx

@@ -0,0 +1 @@
+While this feature isn't currently supported for Ruby or most of its frameworks, it is supported for [Rails](/platforms/ruby/guides/rails/user-feedback/).

src/platform-includes/alert-using-a-framework/ruby.rack.mdx

@@ -0,0 +1,19 @@
+## Crash-Report Modal
+
+Our embeddable, JavaScript-based, Crash-Report modal is useful when you would typically render a plain error page (the classic `500.html`) on your website.
+
+To collect feedback, the Crash-Report modal requests and collects the user's name, email address, and a description of what occurred. When feedback is provided, Sentry pairs the feedback with the original event, giving you additional insights into issues.
+
+The screenshot below provides an example of the Crash-Report modal, though yours may differ depending on your customization:
+
+![An example of a Crash-Report modal with text boxes for user name, email, and additional details about the break.](./user_feedback_widget.png)
+
+### Integration
+
+The modal authenticates with your public DSN, then passes in the Event ID that was generated on your backend.
+
+<PlatformContent includePath="user-feedback/example-widget/" />
+
+## User Feedback API
+
+If you'd prefer an alternative to the modal or do not have a JavaScript frontend, you can use the [User Feedback API](/api/projects/submit-user-feedback/).

src/platform-includes/alert-using-a-framework/ruby.rails.mdx

@@ -22,8 +22,6 @@ All Sentry SDKs support the <PlatformIdentifier name="before-send" /> callback m
 
 Note also that breadcrumbs can be filtered, as discussed in [our Breadcrumbs documentation](/product/error-monitoring/breadcrumbs/).
 
-<PlatformSection notSupported={["apple", "dotnet", "elixir", "rust", "unreal", "kotlin-multiplatform"]}>
-
 #### Event Hints
 
 The <PlatformIdentifier name="before-send" /> callback is passed both the `event` and a second argument, `hint`, that holds one or more hints.
@@ -34,10 +32,6 @@ Typically a `hint` holds the original exception so that additional data can be e
 
 When the SDK creates an event or breadcrumb for transmission, that transmission is typically created from some sort of source object. For instance, an error event is typically created from a log record or exception instance. For better customization, SDKs send these objects to certain callbacks (<PlatformIdentifier name="before-send" />, <PlatformIdentifier name="before-breadcrumb" /> or the event processor system in the SDK).
 
-</PlatformSection>
-
-<PlatformSection notSupported={["native", "apple", "dotnet", "unreal", "elixir", "kotlin-multiplatform"]}>
-
 ### Using Hints
 
 Hints are available in two places:
@@ -71,36 +65,6 @@ In this example, the fingerprint is forced to a common value if an exception of
 
 <PlatformContent includePath="configuration/breadcrumb-hints" />
 
-</PlatformSection>
-
-<PlatformSection supported={["javascript", "node", "go"]} >
-
-### Using <PlatformIdentifier name="ignore-errors" />
-
-You can use the <PlatformIdentifier name="ignore-errors" /> option to filter out errors that match a certain pattern. This option receives a list of strings and regular expressions to match against the error message. When using strings, partial matches will be filtered out, so if you need to filter by exact match, use regex patterns instead.
-
-<PlatformContent includePath="configuration/ignore-errors" />
-</PlatformSection>
-
-<PlatformSection supported={["php"]} >
-
-### Using <PlatformIdentifier name="ignore-exceptions" />
-
-You can use the <PlatformIdentifier name="ignore-exceptions" /> option to filter out errors that match a type or subtype.
-
-<PlatformContent includePath="configuration/ignore-exceptions" />
-</PlatformSection>
-
-<PlatformSection supported={["android", "javascript", "java", "python"]} notSupported={["kotlin-multiplatform"]}>
-
-### Decluttering Sentry
-
-<PlatformContent includePath="configuration/decluttering" />
-
-</PlatformSection>
-
-<PlatformSection supported={["node", "javascript", "python", "php", "dotnet", "java", "ruby", "go", "react-native", "android", "dart"]} notSupported={["javascript.cordova", "unreal", "kotlin-multiplatform"]}>
-
 ## Filtering Transaction Events
 
 To prevent certain transactions from being reported to Sentry, use the <PlatformIdentifier name="traces-sampler" /> or <PlatformIdentifier name="before-send-transaction" /> configuration option, which allows you to provide a function to evaluate the current transaction and drop it if it's not one you want.
@@ -119,30 +83,6 @@ If the transaction currently being processed has a parent transaction (from an u
 
 Learn more about <PlatformLink to="/configuration/sampling/">configuring the sample rate</PlatformLink>.
 
-<PlatformSection supported={["node", "javascript", "php", "go", "python", "java", "ruby"]}>
-
 ### Using <PlatformIdentifier name="before-send-transaction" />
 
 <PlatformContent includePath="configuration/before-send-transaction" />
-
-</PlatformSection>
-
-<PlatformSection supported={["javascript", "node", "go"]} >
-
-### Using <PlatformIdentifier name="ignore-transactions" />
-
-You can use the <PlatformIdentifier name="ignore-transactions" /> option to filter out transactions that match a certain pattern. This option receives a list of strings and regular expressions to match against the transaction name. When using strings, partial matches will be filtered out, so if you need to filter by exact match, use regex patterns instead.
-
-<PlatformContent includePath="configuration/ignore-transactions" />
-</PlatformSection>
-
-<PlatformSection supported={["php"]} >
-
-### Using <PlatformIdentifier name="ignore-transactions" />
-
-You can use the <PlatformIdentifier name="ignore-transactions" /> option to filter out transactions that match a certain string.
-
-<PlatformContent includePath="configuration/ignore-transactions" />
-</PlatformSection>
-
-</PlatformSection>