Mismatched property name for byte-backed `JsonParser.nextNameMatch(PropertyNameMatcher)`

[cowtowncoder]

(note: created based on FasterXML/jackson-databind#5372)

Looks like following JSON can produce property name mismatch:

            {
              "aaaabbbbcccc": "v3",
              "aaaabbbbcccc2": "v4"
            }

via byte-based streaming (UTF8) parser.

Since the original test is on databind, it is unclear on which codepath: either regular canonicalizing parser, or with PropertyNameMatcher (new in 3.0) -- my guess is latter.

Regardless, need to figure it out: so start with test to reproduce.

[cowtowncoder]

Looks like 1-3 "remainder" characters beyond 12 (16, 20, ...) were missing from lookups, leading to wrong match.