Simplify script detection using regular expressions

[1ec5]

Simplified some internationalization-related code to match a given character against a regular expression that tests the Unicode script instead of manually checking whether it falls inside the ranges of a series of Unicode blocks. This is more future-proof because it offloads some decisionmaking onto the browser. Unfortunately, the most verbose methods related to vertical orientation must still be maintained by hand, because the ECMAScript standard doesn’t allow browsers to support the other relevant Unicode character properties. But at least the diff in #4550 will end up a bit shorter as a result.

Fixes #4541.

Launch Checklist

• Confirm your changes do not include backports from Mapbox projects (unless with compliant license) - if you are not sure about this, please ask!
• Briefly describe the changes in this PR.
• Link to related issues.
• Include before/after visuals or gifs if this PR includes visual changes.
• Write tests for all new functionality.
• Document any changes to public APIs.
• Post benchmark scores.
• Add an entry to CHANGELOG.md under the ## main section.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.03%. Comparing base (7324d9a) to head (8cc71e4).
Report is 3 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #4560       +/-   ##
===========================================
+ Coverage   65.31%   88.03%   +22.71%     
===========================================
  Files         247      247               
  Lines       33493    33494        +1     
  Branches     1778     2365      +587     
===========================================
+ Hits        21877    29487     +7610     
+ Misses      10768     3056     -7712     
- Partials      848      951      +103     

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

[HarelM]

I'm having a hard time understanding the difference between the two PR related to these files.
Can we close one of them and move all the changes to one PR?
Currently I'm jumping between one to the other and trying to find the difference, which is less than ideal.
If one could be a PR against another branch or if you want me to merge one of the PR to a branch so that I can see the addition between the two PRs.

[1ec5]

#4560 is now based on #4560 (this PR). The diff in #4560 is cumulative of both PRs, but for the purpose of that PR, I would ask you to ignore the first five commits and focus on the last three commits. Unfortunately, I can’t tell GitHub to set the target of that branch to this branch, because I created both PRs from a fork.

I recommend first reviewing the changes in #4560 (this PR), as suggested in #4550 (comment). If you agree, merge this PR to main; then #4560 will automatically rebase atop main to become much simpler without these five commits.

[HarelM]

Ok, I'll review this first.
Is it ready for review now?

[1ec5]

Sure, have at it!