fix(profiling-node): Respect profileSessionSampleRate in trace profile lifecycle

[Jxxunnn]

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).
• Link an issue if there is one related to your pull request. If no issue is linked, one will be auto-generated and linked.

Closes #22927

When using the trace profile lifecycle in @sentry/profiling-node, trace lifecycle profiling was set up without checking the session sampling decision. As a result, chunk profiling would start on span start even when profileSessionSampleRate resulted in an unsampled session.

This change skips trace lifecycle profiling setup when the session is not sampled, ensuring that profileSessionSampleRate is respected in the trace lifecycle as well.

A regression test was added for profileSessionSampleRate: 0 with the trace profile lifecycle.

[Lms24]

Hey @Jxxunnn thanks for reporting and fixing this! You're right this looks like a bug. I formatted and rebased your PR to get CI passing. Will merge soon and also take care of releasing the fix in the next v10 version.

[Lms24]

One thing to note: this change now requires that profileSessionSampleRate is set to enable profiling (as we saw in the test adjustments). This is how we intended it. Just might break some people who set up profiling incorrectly. I think this is fine/acceptable, given we fixed incorrect behaviour.