Optional leading plus sign not included in textual value of any integral nor all floating-point numbers

[cowtowncoder]

Implementation of #774 is mostly complete, but there is one minor inconsistency: whereas leading plus sign -- if (and only if) enabled as non-standard feature -- is retained for some floating-point numbers when accessing token with JsonParser.getText() (and related), it is not retained for any of integral numbers (nor all FPs).

The underlying problem to solve is that of assumptions based on there only ever being a leading minus sign in TextBuffer (or shared input buffer): something that made sense before allowing non-standard leading plus.

[cowtowncoder]

Come to think of this, one option is to remove leading plus sign from all cases, instead of trying to add it.
This is not ideal but is possible.

[cowtowncoder]

Ok, so: currently non-standard plus (+) is never included in text returned. This is different from other deviations, partly since they are omissions (lack of leading 0, or trailing digit after decimal comma).
I guess comparison could be to leading zeroes, handling of which (in non-standard) mode I don't actually know.
But if they are not exposed we could even consider current behavior as the expected way (leave out non-standard characters). Have to think more about this -- then again it will take some effort to retain plus sign anyway so there is no urgency.

[cowtowncoder]

Current thinking: getText() should faithfully reproduce input token -- so leading plus, even if non-standard, should be included.