Spilt Tagged<T> into a utility crate

[HalidOdat]

Depends on #3837

This makes Tagged<T> be usable in boa_string and boa_engine.

[github-actions]

Test262 conformance changes

Test result	main count	PR count	difference
Total	50,731	50,731	0
Passed	42,973	42,973	0
Ignored	1,395	1,395	0
Failed	6,363	6,363	0
Panics	18	18	0
Conformance	84.71%	84.71%	0.00%

[nekevss]

General discussion on utility crates: how do we want to go about handling utilities in general that's going to be best for maintenance in the long term?

Should we have one general boa_utils crate or a utils directory with individual crates hosted inside it (I'm thinking of icu4x's structure as an example). We could also extract SmallMap into the utils as well. Both Tagged and SmallMap could then be standalone crates unto themselves.

There's some benefits to taking the utils directory approach.

1. The code is more modular.
2. Offers the libraries for generic use case for the Rust ecosystem as a whole.
3. Could provide some soft "marketing" for boa, so to speak.

There could be a pretty big negative around the maintenance complexity utility crates may cause and managing separate releases may actually end being a large headache. 😕

Any thoughts?

[HalidOdat]

Hmmm... Tagged<T> and SmallMap are very small (single file) so don't think it's going to need that much maintenance. Just a thought: we could put them in separate repos (like we do with ryu-js, and temporal_rs) may make it easier to separately publish the crates.

What does the rest of the team say? @jedel1043 @raskad @Razican

[Razican]

From my side, in general, if the crate / code makes sense outside Boa, then we should make it separate, so that others can benefit from it. If not, I would keep it in.

For this case, it seems these types could be used outside of Boa, and they have no dependency on the engine, so I would make them separate if it's not too much maintenance burden (and we don't forget to maintain them 😅)