Fix leaking field name text in IonCursorBinary

[popematt]

Issue #, if available:

None

Description of changes:

There is a bug that I discovered where Ion 1.1 binary data such as E0 01 01 EA FD 0F 01 FF 61 D3 09 A1 62 (equivalent to $ion_1_1 {a:{$4:b}}) is interpreted incorrectly. The field text from a was not properly being reset and was leaking into the next field name, so that even though $4 was being parsed correctly the reader would see that field text was available and return that instead. I was only able to reproduce this for cases such as mentioned above where there is a field name with inline text and then the first nested field inside that value is a SID field name.

The bug was fixed by clearing fieldTextMarker in the reset() method. Since this is the second such bug I've found related to things not being cleared in the reset() method, I also decided to preemptively add a few more things to the reset() method in the hopes that it will spare us from some obscure problem in the future.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (ion-11-encoding@9b17d94). Click here to learn what that means.

Additional details and impacted files

@@                Coverage Diff                 @@
##             ion-11-encoding     #859   +/-   ##
==================================================
  Coverage                   ?   68.82%           
  Complexity                 ?     6221           
==================================================
  Files                      ?      182           
  Lines                      ?    25104           
  Branches                   ?     4470           
==================================================
  Hits                       ?    17278           
  Misses                     ?     6468           
  Partials                   ?     1358           

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