feat(grit): parse Grit literal snippets

[arendjr]

Summary

Grit patterns can contain snippet literals like such:

`console.log("foo");`

The part inside the backticks is a structural pattern that matches any function call node where the callee matches console.log and which has a single string argument with the content foo.

This PR updates the Grit crates and implements the parsing for snippet literals, so that our own Grit bindings invoke the Biome JS parser when a snippet like the above is encountered.

Test Plan

Added a quick test that helps with testing Grit patterns, although it still fails in the execution part. But at least it parses the query with a literal snippet now.

[codspeed-hq]

CodSpeed Performance Report

Merging #3051 will not alter performance

_{Comparing arendjr:grit-literal-parser (47e2cd8) with arendjr:grit-literal-parser (eac93bf)}

Summary

✅ 92 untouched benchmarks

[ematipico]

I left some suggestions that might help to improve the code

[ematipico]

I am not sure about the intention of this code, but we have a utility to extract columns and rows from the source code, I suggest to look here and see how we use it:

biome/crates/biome_diagnostics/src/display_github.rs

Lines 30 to 32 in cd6e830

	let source = SourceFile::new(source_code);
	let start = source.location(span.start())?;
	let end = source.location(span.end())?;

[ematipico]

We have an utility called markup_to_string that you might want to look at:

biome/crates/biome_json_analyze/src/lib.rs

Lines 152 to 154 in cd6e830

	let text = markup_to_string(markup! {
	{PrintDiagnostic::verbose(&error)}
	});

[arendjr]

Unfortunately that one is only available in the biome_cli crate. I'll see how far we get with the description and range. If necessary, I'll try to move the util.

[ematipico]

It's not exactly that one, but we have it

biome/crates/biome_diagnostics/src/lib.rs

Lines 74 to 92 in 105f628

	pub fn print_diagnostic_to_string(diagnostic: &Error) -> String {
	let mut buffer = termcolor::Buffer::no_color();
	Formatter::new(&mut Termcolor(&mut buffer))
	.write_markup(markup! {
	{PrintDiagnostic::verbose(diagnostic)}
	})
	.expect("failed to emit diagnostic");
	let mut content = String::new();
	writeln!(
	content,
	"{}",
	std::str::from_utf8(buffer.as_slice()).expect("non utf8 in error buffer")
	)
	.unwrap();
	content
	}

[ematipico]

It might be worth leaving a comment explaining what we are trimming here, e.g. why there is a 1 and a -1. For example, I don't know, even though I can guess it by looking at the PR

[ematipico]

I noticed a lot of to_owned in this PR. Internally, we prefer to use to_string whenever possible unless it's a type that needs to use this function.