Investigate the performance impacts of removing String.count, String.offset,
and String.hashcode on various industry standard benchmarks.
There are no new regression tests for this change because the API is not impacted. It is a behind-the-scenes performance/implementation change only
A working change has been developed that allows a version
of the String class that doesn't use the count/offset fields.
However, it's not possible to eliminate the hashcode field.
This fix also works with compressed strings.
At this point, the fix is on hold as other priorities have