fix(tracing): Trim idle transaction spans if they exceed final timeout

[AbhiPrasad]

Supercedes #8505

resolves #8504

If an idle transaction's duration is longer than final timeout + idle timeout, opt to not capture and send it to Sentry.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	75.07 KB (+0.09% 🔺)
@sentry/browser (incl. Tracing) - Webpack (gzipped)	31.4 KB (+0.16% 🔺)
@sentry/browser - Webpack (gzipped)	21.95 KB (0%)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	69.79 KB (+0.05% 🔺)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	28.28 KB (+0.12% 🔺)
@sentry/browser - ES6 CDN Bundle (gzipped)	20.33 KB (+0.02% 🔺)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	220.89 KB (+0.05% 🔺)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	85.99 KB (+0.11% 🔺)
@sentry/browser - ES6 CDN Bundle (minified & uncompressed)	60.48 KB (0%)
@sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	30.41 KB (+0.12% 🔺)
@sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	65.14 KB (0%)
@sentry/react - Webpack (gzipped)	21.96 KB (0%)
@sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	92.91 KB (+0.07% 🔺)
@sentry/nextjs Client - Webpack (gzipped)	50.89 KB (+0.11% 🔺)

[krystofwoldrich]

Dropping the span that goes over the final timeout sounds like a good quick solution. 👍

[krystofwoldrich]

Looks good. 🚀

I think maybe we should fo a small troubleshooting docs update for people running into the long Tx.

[AbhiPrasad]

I think maybe we should fo a small troubleshooting docs update for people running into the long Tx.

Good idea, let me put in my todo!