📎 Remove dynamic registration for formatting from the LSP

[ematipico]

Description

At the moment, the formatting capabilities of the LSP are registered using dynamic capabilities:

biome/crates/biome_lsp/src/server.rs

Lines 159 to 189 in 6739a51

	capabilities.add_capability(
	"biome_formatting",
	"textDocument/formatting",
	if self.session.is_linting_and_formatting_disabled() {
	CapabilityStatus::Disable
	} else {
	CapabilityStatus::Enable(None)
	},
	);
	capabilities.add_capability(
	"biome_range_formatting",
	"textDocument/rangeFormatting",
	if self.session.is_linting_and_formatting_disabled() {
	CapabilityStatus::Disable
	} else {
	CapabilityStatus::Enable(None)
	},
	);
	capabilities.add_capability(
	"biome_on_type_formatting",
	"textDocument/onTypeFormatting",
	if self.session.is_linting_and_formatting_disabled() {
	CapabilityStatus::Disable
	} else {
	CapabilityStatus::Enable(Some(json!(DocumentOnTypeFormattingRegistrationOptions {
	document_selector: None,
	first_trigger_character: String::from("}"),
	more_trigger_character: Some(vec![String::from("]"), String::from(")")]),
	})))
	},
	);

This was done by leveraging the "update configuration and enable/disable" formatting, although this isn't needed because the workspace takes care of it. Plus, some LSP services out there don't support dynamic capabilities (or they do in a limited way).

We should remove the dynamic registration for formatting.