src: move all 1-byte encodings to native

[ChALkeR]

Tracking: #61041

This builds on top of #61093 and gives an additional ~2x improvement by moving the same logic to native

Warning

Very crude, just a concept demonstration at this point

The current native fast path removed in #61093 has a bunch of nested ifs and converts data from utf16 to utf8 and then back to utf16
This instead constructs strings using direct maps as #61093 and returns them as raw buffers

windows-1252, main:

Test	Size	Throughput	Mean Time
Latin lipsum (ASCII)	84.902 KiB	0.31 GiB/s	0.272 ms
Complex 1	79.771 KiB	0.06 GiB/s	1.292 ms

windows-1252, #61093:

Test	Size	Throughput	Mean Time
Latin lipsum (ASCII)	84.902 KiB	33.41 GiB/s	0.003 ms
Complex 1	79.771 KiB	1.48 GiB/s	0.056 ms

windows-1252, this PR:

Test	Size	Throughput	Mean Time
Latin lipsum (ASCII)	84.902 KiB	36.83 GiB/s	0.002 ms
Complex 1	79.771 KiB	3.11 GiB/s	0.027 ms

This also similarly improves all other 1-byte encodings compared to #61093

Only the second commit, first is #61093

Warning

Has a lot of cleanup to do, do mot merge, reviewing except for benchmarking / concept is pointless at this point

---

For comparison, Bun:

Test	Size	Throughput	Mean Time
Latin lipsum (ASCII)	84.902 KiB	36.89 GiB/s	0.003 ms
Complex 1	79.771 KiB	0.23 GiB/s	0.329 ms

v8/jsc is not an issue, unoptimal code is

cc @nodejs/performance

[nodejs-github-bot]

Review requested:

• @nodejs/startup

[mcollina]

I guess you don’t need this array long term. Can you create it inline with the Set?