feat: shorter framework names

[feugy]

📓 What's in there?

When reporting vitals and metrics, we should use a shorter framework name to avoid very long values like @vercel/speed-insights/sveltekit

A shorter prefix like vercel should be enough, and will give vercel/next, vercel/sveltekit or vercel/nuxt

🧪 How to test?

Have a try at one of our deployments, with dev tools open on network, filtering for vitals

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
speed-insights-nextjs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 28, 2023 2:07pm
speed-insights-nuxt	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 28, 2023 2:07pm
speed-insights-remix	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 28, 2023 2:07pm
speed-insights-sveltekit	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 28, 2023 2:07pm
speed-insights-vue	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 28, 2023 2:07pm

[linear[bot]]

ALY-1087 A shorten framework name for @vercel/speed-insights

When reporting vitals and metrics, we should use a shorter framework name to avoid very long values like `vercel/speed-insights/sveltekit` A shorter prefix like `vercel` should be enough, and will give `vercel/next`, `vercel/sveltekit` or `vercel/nuxt`

[feugy]

We concluded that we can afford these long names. At least they are explicit!