fix(lsp): register formatter dynamically if possible

[nhedger]

Summary

This PR changes the way the formatting providers are registered by the LSP to prevent registering a formatter twice.

The problem

Some LSP clients do not support dynamic registration for formatting providers, so in PR #1042 , we explicitly enabled static registration of the formatters. Unfortunately, this caused clients that support dynamic registration to show two formatters (the statically registered one, and the dynamically registered one).

The solution

This PR adds logic to detect whether the clients supports dynamic registration of formatters, and skips the static registration when they do.

Test Plan

• Ensure only one formatter is registered in VS Code's Format Document with... menu.

Fixes #1584

[netlify]

✅ Deploy Preview for biomejs ready!

Name	Link
🔨 Latest commit	d0a4822
🔍 Latest deploy log	https://app.netlify.com/sites/biomejs/deploys/65a935121e0c09000821cf69
😎 Deploy Preview	https://deploy-preview-1590--biomejs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 94 (🔴 down 6 from production) Accessibility: 97 (no change from production) Best Practices: 100 (no change from production) SEO: 93 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ematipico]

It looks great! Can you add a changelog line before merging?

[nhedger]

It looks great! Can you add a changelog line before merging?

I've added the changelog entry under a new LSP header, hope that makes sense.

[ematipico]

Cool, you'll have to run just gen-web, commit and merge :D thank you!

[nhedger]

Thanks for the assist, much appreciated!