test(node-integration): Replace conditionalTest with a supports helper

[JPeer264]

Pro Tip: It is better to review it with the option "Hide whitespaces": https://github.com/getsentry/sentry-javascript/pull/25202/changes?w=1

This replaces conditionalTest with a supports(requirements) helper that returns a boolean, so blocks and single tests use the same requirements with Vitest's runIf. The RUNTIME checks in skipIf use it too, and skipRuntimes becomes runtimes, the runtimes that run the tests.

describe.runIf(supports({ min: 22 }))('OpenAI integration (V7)', () => {
  test.runIf(supports({ runtimes: ['node'] }))('...', async () => {});
});

Most of the diff is new indentation. Hide whitespace to review.

Why

Blocks used conditionalTest(options) and single tests used skipIf with a RUNTIME check, so one condition had two forms. With one helper, a new requirement, for example a minimum Bun version, works for both.

API decisions

The helper goes with runIf, not skipIf, so each requirement says where the tests run, and a call does not read as skipIf(shouldSkip({ skipRuntimes })). runIf cannot take the requirements object directly, because Vitest only checks if the value is truthy. Wrapping Vitest's test and describe would allow it, but then an object passed to Vitest's own functions would always run.

[JPeer264]

bugbot run

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 0ef01b6. Configure here.}

[andreiborza]

Could we also add a bugbot review rule or a linting rule to use support over the older stuff?

[JPeer264]

@andreiborza good idea, will do in a follow up 👍