MD view does not respect onboarding options

[chargome]

Steps to Reproduce

e.g. https://docs.sentry.io/platforms/javascript/guides/react.md has several duplicate steps in the markdown. This is because the steps are displayed dynamically depending on which onboarding options are selected.

Not entirely sure how a good solution would look like, maybe we just should get rid of the steps in the MD?

Expected Result

No duplicate steps

Actual Result

Duplicate steps

Additional Info

No response

[chargome]

cc @BYK

[BYK]

If you can be more specific about the "duplicate steps" part I can think of a solution.

I tend to remove in these scenarios unless we can find a way to make this work in plain text and express the context for that section.

[chargome]

e.g.

## [Step 5: Capture Redux State Data (Optional)](https://docs.sentry.io/.md#step-5-capture-redux-state-data-optional)

## [Step 4: Capture Redux State Data (Optional)](https://docs.sentry.io/.md#step-4-capture-redux-state-data-optional)

[BYK]

@chargome okay I found the component responsible for this:

sentry-docs/src/components/onboarding/index.tsx

Line 143 in 9f4a974

export function OnboardingOption({

The issue is, its API makes no sense to me. Sample usage:

<OnboardingOption optionId="performance">
  ## Step 6: Add Readable Stack Traces With Source Maps (Optional)
</OnboardingOption>
<OnboardingOption optionId="performance" hideForThisOption>
  ## Step 5: Add Readable Stack Traces With Source Maps (Optional)
</OnboardingOption>

What controls hideForThisOption? Both say optionId="performance". Does this mean "Step 5" version should be hidden when performance option is selected?

I think we need to reafactor this logic to conform to the following:

1. Make step numbering dynamic (use an <ol> or something?)
2. Make this declarative like <OnboardingFor options="performance profiling"> or something along these lines

Then if we emit this information in a data- attribute, I can make a decision to render which variant (I'd go for everything on version). Actually, at that point I wouldn't need to make a decision as I wanna show everything enabled version anyway so we just hide these dynamically on the HTML version of the docs.

Makes sense?