perf: optimize validate http token

[PandaWorker]

This relates to...

Header name validation performance

Changes

Status

• I have read and agreed to the Developer's Certificate of Origin
• Tested
• Benchmarked (optional)
• [] Documented
• Review ready
• In review
• Merge ready

[PandaWorker]

This implementation has already been added to node.

nodejs/node#59832

[mcollina]

Great work! How much do we gain?

[mcollina]

Can you please remove the isTokeCharCode function and just inline the change?

[PandaWorker]

Done)

[codecov-commenter]

Codecov Report

❌ Patch coverage is 96.29630% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 92.93%. Comparing base (6365a90) to head (d3c5f6e).
⚠️ Report is 25 commits behind head on main.

Files with missing lines	Patch %	Lines
lib/core/util.js	96.29%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff            @@
##           main    #4608       +/-   ##
=========================================
+ Coverage      0   92.93%   +92.93%     
=========================================
  Files         0      106      +106     
  Lines         0    32971    +32971     
=========================================
+ Hits          0    30640    +30640     
- Misses        0     2331     +2331     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[PandaWorker]

Great work! How much do we gain?

I didn't just take the number 12 for validation through a regular expression, it's after 12 characters that the problems start in the fast version, it's probably something to do with v8 optimization for short strings.

Here is a benchmarking of the validation of strings from 8 to 20 characters

[metcoder95]

lgtm with Matteo's comment

[mcollina]

lgtm