feat(tracing): Do not create interactions if navigation or pageload transaction active

[0Calories]

Fixes a slight annoyance where interaction transactions would still be created alongside a pageload or navigation transaction. Both transactions at this point would have the same spans, so there's no need to duplicate them.

This scenario occurs when clicking a link in an SPA, basically whenever browserHistory.push is being called to perform a soft navigation.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	20.62 KB (-0.01% 🔽)
@sentry/browser - ES5 CDN Bundle (minified)	64.4 KB (0%)
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	19.15 KB (-0.02% 🔽)
@sentry/browser - ES6 CDN Bundle (minified)	56.78 KB (0%)
@sentry/browser - Webpack (gzipped + minified)	21.53 KB (0%)
@sentry/browser - Webpack (minified)	72 KB (0%)
@sentry/react - Webpack (gzipped + minified)	21.55 KB (0%)
@sentry/nextjs Client - Webpack (gzipped + minified)	52.02 KB (+0.1% 🔺)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	28.18 KB (+0.08% 🔺)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	26.38 KB (+0.07% 🔺)
@sentry/replay ES6 CDN Bundle (gzipped + minified)	44.74 KB (-0.01% 🔽)
@sentry/replay - Webpack (gzipped + minified)	38.86 KB (0%)
@sentry/browser + @sentry/tracing + @sentry/replay - ES6 CDN Bundle (gzipped + minified)	63.43 KB (+0.04% 🔺)
@sentry/browser + @sentry/replay - ES6 CDN Bundle (gzipped + minified)	56.49 KB (-0.01% 🔽)

[AbhiPrasad]

We can merge after lint is fixed!

[AbhiPrasad]

Pushed up linting fix so we can merge for release today.