html_escape: Avoid buffer allocation for strings with no escapable character

[noteflakes]

The existing html_escape implementation always allocates buffer space (6 times
the length of the input string), even when the input string does not contain any
character that needs to be escaped.

This PR modifies the implementation of optimized_escape_html to not
pre-allocate an output buffer, but instead allocate it on the first occurence of
a character that needs escaping. In addition, instead of copying non-escaped
characters one by one to the output buffer, continuous non-escaped segments of
characters are copied using memcpy.

A synthetic benchmark employing the input strings used in the test_html_escape
method in test/test_erb.rb shows the modified implementation to be about 35%
faster than the original:

ruby 3.5.0preview1 (2025-04-18 master d06ec25be4) +YJIT +PRISM [x86_64-linux]
Warming up --------------------------------------
escape old 273.773k i/100ms
escape new 369.558k i/100ms
Calculating -------------------------------------
escape old 2.766M (± 1.6%) i/s (361.48 ns/i) - 13.962M in 5.048625s
escape new 3.765M (± 2.0%) i/s (265.58 ns/i) - 18.847M in 5.007869s
Comparison:
escape old: 2766396.0 i/s
escape new: 3765317.7 i/s - 1.36x faster

[p8]

Thanks @noteflakes ! Is this optimization also possible in CGI#escape_html?
Also wondering if this should be duplicated in both gems...
https://github.com/ruby/cgi/blob/9d9a2eb868483fbf71d8e47d51d7b237d3867409/ext/cgi/escape/escape.c

[noteflakes]

Thanks @noteflakes ! Is this optimization also possible in CGI#escape_html? Also wondering if this should be duplicated in both gems... https://github.com/ruby/cgi/blob/9d9a2eb868483fbf71d8e47d51d7b237d3867409/ext/cgi/escape/escape.c

Sure, I'll make a PR for CGI too.

[k0kubun]

Also wondering if this should be duplicated in both gems...

They have slightly different hehaviors. ERB's is faster than CGI's, and replacing CGI's with ERB's would be a breaking change, which is why they are deliberately separate.