refactor(biome_deserialize): add deserilization context

[Conaclos]

Summary

This is a BREAKING CHANGE for library consumers.

This implements the design proposed in this comment.

The context allows reporting diagnostics and to retrieve the identifier of the root object.
The identifier can be anything. It can notably be the path to the deserialized file: what was requested here.

Note that deserialize_from_json_str and deserialize_from_json_ast last argument was previously passed as name to the deserializer.
It is now used as identifier.
The name of the root deserializer is always set to the empty string.

Also I removed the passthrough_name derive macro attribute. This attribute was introduced to allow to pass a name between deserializers. It is no longer needed since we have ctx.id().

NOTE: we no longer need this refactor. However, this could be good to merge.
We should check with our library consumers if it is something they still require.

Test Plan

CI must pass.

[github-actions]

Parser conformance results on

js/262

Test result	main count	This PR count	Difference
Total	48517	48517	0
Passed	47326	47326	0
Failed	1191	1191	0
Panics	0	0	0
Coverage	97.55%	97.55%	0.00%

jsx/babel

Test result	main count	This PR count	Difference
Total	40	40	0
Passed	37	37	0
Failed	3	3	0
Panics	0	0	0
Coverage	92.50%	92.50%	0.00%

symbols/microsoft

Test result	main count	This PR count	Difference
Total	6574	6574	0
Passed	2203	2203	0
Failed	4371	4371	0
Panics	0	0	0
Coverage	33.51%	33.51%	0.00%

ts/babel

Test result	main count	This PR count	Difference
Total	680	680	0
Passed	608	608	0
Failed	72	72	0
Panics	0	0	0
Coverage	89.41%	89.41%	0.00%

ts/microsoft

Test result	main count	This PR count	Difference
Total	18473	18473	0
Passed	14146	14146	0
Failed	4327	4327	0
Panics	0	0	0
Coverage	76.58%	76.58%	0.00%

[codspeed-hq]

CodSpeed Performance Report

Merging #4166 will not alter performance

_{Comparing conaclos/deserialize-context (f024c39) with next (2481b08)}

Summary

✅ 101 untouched benchmarks

[ematipico]

Usually, breaking changes should be presented with a clear migration path for users.

I know that we don't have a changelog for the crate yet, but maybe we should. As for now, I think we should have at least a migration path in the description of the PR.

Not intended

[ematipico]

Can you point this to next instead? So we can create a changeset for biome_deserialize