ref(tracing): Add FID element to frontend transactions

[k-fish]

This will add the FID element so that it's possible to tell which element is involved in the delay, which is extremely helpful for debugging.

[github-actions]

⚠️ This PR is opened against master. You probably want to open it against develop.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser (incl. Tracing, Replay) - Webpack (gzipped)	84.27 KB (+0.04% 🔺)
@sentry/browser (incl. Tracing) - Webpack (gzipped)	31.44 KB (+0.09% 🔺)
@sentry/browser - Webpack (gzipped)	22 KB (0%)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped)	78.8 KB (+0.04% 🔺)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped)	28.62 KB (+0.11% 🔺)
@sentry/browser - ES6 CDN Bundle (gzipped)	21 KB (0%)
@sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed)	254.44 KB (+0.03% 🔺)
@sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed)	86.72 KB (+0.07% 🔺)
@sentry/browser - ES6 CDN Bundle (minified & uncompressed)	62.35 KB (0%)
@sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped)	31.48 KB (+0.08% 🔺)
@sentry/react (incl. Tracing, Replay) - Webpack (gzipped)	84.3 KB (+0.04% 🔺)
@sentry/react - Webpack (gzipped)	22.05 KB (0%)
@sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped)	102.26 KB (+0.03% 🔺)
@sentry/nextjs Client - Webpack (gzipped)	51.02 KB (+0.06% 🔺)

[mydea]

Is this still something we want to do, or can we close this PR? @k-fish

[andreiborza]

@k-fish is this still something we want or can we close this PR?

[k-fish]

@andreiborza we should add element for FID, though I'm not sure setTag will be the preferred approach going forward.

[Lms24]

Given web-vitals dropped support for FID and we'll likely remove sending FID in v10/11 (#16560, also synced with the performance team on this), I'd close this PR.

@k-fish let me know if we should still ship the element in the meantime