fix: update build command to include pre-build steps (#15686)

<!-- Use this checklist to make sure your PR is ready for merge. You may
delete any sections you don't need. -->

## DESCRIBE YOUR PR
This is a fix to remedy a regression introduced in PR  #15637. 

That PR pre-computes the doc tree at build time with `generate-doctree`.
However the 404-lint job was using `yarn next build`, which skips
pre-build steps so the doctree was not available causing a failure.

Also fixed subsequent broken links that were caught by the now
functioning 404 check.

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [ ] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

## LEGAL BOILERPLATE

<!-- Sentry employees and contractors can delete or ignore this section.
-->

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)

Author: jaffrepaul

.github/workflows/lint-404s.yml

@@ -42,7 +42,7 @@ jobs:
 
       - run: yarn install --frozen-lockfile
 
-      - run: yarn next build
+      - run: yarn build
         if: steps.filter.outputs.docs == 'true'
         env:
           SENTRY_DSN: https://[email protected]/0

docs/platforms/apple/common/migration/index.mdx

@@ -50,7 +50,11 @@ HTTP client errors now mark sessions as errored. This provides better visibility
 
 ### Profiling Changes
 
-We removed all deprecated profiling APIs in version [9.0.0](https://github.com/getsentry/sentry-cocoa/releases/tag/9.0.0). The only supported profiling method is now <PlatformLink to="/profiling/#enable-ui-profiling">UI Profiling</PlatformLink> (also known as continuous V2 profiling), which was introduced in [version 8.49.0](https://github.com/getsentry/sentry-cocoa/releases/tag/8.49.0).
+We removed all deprecated profiling APIs in version [9.0.0](https://github.com/getsentry/sentry-cocoa/releases/tag/9.0.0).
+
+<PlatformSection notSupported={["apple.tvos", "apple.watchos", "apple.visionos"]}>
+
+The only supported profiling method is now <PlatformLink to="/profiling/#enable-ui-profiling">UI Profiling</PlatformLink> (also known as continuous V2 profiling), which was introduced in [version 8.49.0](https://github.com/getsentry/sentry-cocoa/releases/tag/8.49.0).
 
 **Removed deprecated profiling options from `SentryOptions`:**
 - `profilesSampleRate` - used for transaction-based profiling (deprecated)
@@ -75,6 +79,8 @@ SentrySDK.start { options in
 
 For more information, see the <PlatformLink to="/profiling/#enable-ui-profiling">UI Profiling documentation</PlatformLink>.
 
+</PlatformSection>
+
 ### Breaking Changes
 
 #### Option Changes

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

@@ -560,7 +560,7 @@ A number between `0` and `1` that sets the percentage of how many sessions shoul
 
 Determines how profiling sessions are controlled. It has two modes:
 
-- `'manual'` (default): You control when profiling starts and stops using the `startProfiler()` and `stopProfiler()` functions. In this mode, profile sampling is only affected by `profileSessionSampleRate`. Read more about these functions in the <PlatformLink to="/profiling">profiling API documentation</PlatformLink>.
+- `'manual'` (default): You control when profiling starts and stops using the `startProfiler()` and `stopProfiler()` functions. In this mode, profile sampling is only affected by `profileSessionSampleRate`.<PlatformSection notSupported={["javascript.bun", "javascript.cordova", "javascript.capacitor", "javascript.deno", "javascript.cloudflare"]}> Read more about these functions in the <PlatformLink to="/profiling">profiling API documentation</PlatformLink>.</PlatformSection>
 - `'trace'`: Profiling starts and stops automatically with transactions, as long as tracing is enabled. The profiler runs as long as there is at least one sampled transaction. In this mode, profiling is affected by both `profileSessionSampleRate` and your tracing sample rate (`tracesSampleRate` or `tracesSampler`).
 
 </SdkOption>
@@ -597,7 +597,7 @@ A number between `0` and `1` that sets the percentage of how many sessions shoul
 
 Determines how profiling sessions are controlled. It has two modes:
 
-- `'manual'` (default): You control when profiling starts and stops using the `startProfiler()` and `stopProfiler()` functions. In this mode, profile sampling is only affected by `profileSessionSampleRate`. Read more about these functions in the <PlatformLink to="/profiling">profiling API documentation</PlatformLink>.
+- `'manual'` (default): You control when profiling starts and stops using the `startProfiler()` and `stopProfiler()` functions. In this mode, profile sampling is only affected by `profileSessionSampleRate`.<PlatformSection notSupported={["javascript.bun", "javascript.cordova", "javascript.capacitor", "javascript.deno", "javascript.cloudflare"]}> Read more about these functions in the <PlatformLink to="/profiling">profiling API documentation</PlatformLink>.</PlatformSection>
 - `'trace'`: Profiling starts and stops automatically with transactions, as long as tracing is enabled. The profiler runs as long as there is at least one sampled transaction. In this mode, profiling is affected by both `profileSessionSampleRate` and your tracing sample rate (`tracesSampleRate` or `tracesSampler`).
 
 </SdkOption>

docs/product/user-feedback/index.mdx

@@ -7,17 +7,17 @@ og_image: /og-images/product-user-feedback.png
 
 Sentry automatically detects errors thrown by your application, such as performance issues and user experience problems like rage clicks. But there are other frustrations your users may encounter (broken permission flows, broken links, typos, misleading UX, business logic flaws, and so on).
 
-That’s where Sentry’s User Feedback Widget and Crash-Report Modal features come in. Setting up one or both lets you collect feedback from your end-users when they run into bugs in your application. Sentry then links that feedback to available rich debugging context, including errors, replays, and tags such as URL, allowing you to get to the root of the problem faster.
+That's where Sentry's User Feedback Widget and Crash-Report Modal features come in. Setting up one or both lets you collect feedback from your end-users when they run into bugs in your application. Sentry then links that feedback to available rich debugging context, including errors, replays, and tags such as URL, allowing you to get to the root of the problem faster.
 
 For example, using [Session Replay](/product/explore/session-replay/) with the User Feedback Widget could save you time, helping you quickly understand the context of the user problem by seeing exactly what they experienced before submitting their feedback.
 
 ## User Feedback Widget
 
-The User Feedback Widget is an out-of-the-box, persistent widget you can add anywhere on your web application. It allows users to submit feedback quickly and easily any time they encounter something that isn’t working as expected. Learn more about how to install and customize it [here](/product/user-feedback/setup/) and recommended best practices [here](/product/sentry-basics/user-feedback-basics/).
+The User Feedback Widget is an out-of-the-box, persistent widget you can add anywhere on your web application. It allows users to submit feedback quickly and easily any time they encounter something that isn't working as expected. Learn more about how to install and customize it [here](/product/user-feedback/setup/) and recommended best practices [here](/product/sentry-basics/user-feedback-basics/).
 
 ![User Feedback widget.](./img/user-feedback-widget.png)
 
-Feedback collected via the Feedback Widget may have some or all of the following information (depending on what you mark as required and what’s available from the error context):
+Feedback collected via the Feedback Widget may have some or all of the following information (depending on what you mark as required and what's available from the error context):
 
 - Description from the user
 - Screenshot from the user
@@ -46,7 +46,7 @@ We also provide an API to send user feedback programmatically. This allows you t
 
 ## Where to View User Feedback
 
-Whether you choose to collect user feedback via the Feedback Widget, the Crash-Report Modal, or both, you’ll be able to view it from the **User Feedback** page. The page is chronologically-organized with the most recent, unresolved feedback at the top. You can click on individual feedback to see more details all in one view, similar to your e-mail inbox. The right-hand side shows the **User Feedback Details** view, which includes the user’s description and any available debugging context.
+Whether you choose to collect user feedback via the Feedback Widget, the Crash-Report Modal, or both, you'll be able to view it from the **User Feedback** page. The page is chronologically-organized with the most recent, unresolved feedback at the top. You can click on individual feedback to see more details all in one view, similar to your e-mail inbox. The right-hand side shows the **User Feedback Details** view, which includes the user's description and any available debugging context.
 
 You can narrow down the results in the feedback list by using the project, environment, and date range filters.
 
@@ -100,7 +100,7 @@ If your organization has enabled Generative AI Features, Sentry will auto-detect
 
 To make automatic spam detection possible, we use a Large Language Model that classifies messages. This language model is internal to Google Cloud Platform and no data is stored or persisted. This is part of our existing [sub-processor agreement](https://sentry.io/legal/dpa/#subprocessors).
 
-If you’d like to opt out of spam detection, turn off "Enable Spam Detection" in [Settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/) > Projects > [Project Name] > User Feedback (under “Project”).
+If you'd like to opt out of spam detection, turn off "Enable Spam Detection" in [Settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/) > Projects > [Project Name] > User Feedback (under “Project”).