npe when parsing valid bigdecimal

[pjfanning]

Adds test case based on FasterXML/jackson-core#1162

Only seems to have when char[] or byte[] is passed, not when String input is used.

java.lang.NullPointerException: Cannot invoke "java.util.Map.get(Object)" because "powersOfTen" is null
	at ch.randelshofer.fastdoubleparser.ParseDigitsTaskCharArray.parseDigitsRecursive(ParseDigitsTaskCharArray.java:82)
	at ch.randelshofer.fastdoubleparser.JavaBigDecimalFromCharArray.valueOfBigDecimalString(JavaBigDecimalFromCharArray.java:305)
	at ch.randelshofer.fastdoubleparser.JavaBigDecimalFromCharArray.parseBigDecimalStringWithManyDigits(JavaBigDecimalFromCharArray.java:241)
	at ch.randelshofer.fastdoubleparser.JavaBigDecimalFromCharArray.parseBigDecimalString(JavaBigDecimalFromCharArray.java:41)
	at ch.randelshofer.fastdoubleparser.JavaBigDecimalParser.parseBigDecimal(JavaBigDecimalParser.java:197)
	at ch.randelshofer.fastdoubleparser.JavaBigDecimalParser.parseBigDecimal(JavaBigDecimalParser.java:178)
	at ch.randelshofer.fastdoubleparser.JavaBigDecimalLargeInputTest.testLongValidStringFastParse(JavaBigDecimalLargeInputTest.java:18)

The NPE happens because the following line passes a null value (explicitly) for the powersOfTen param.

FastDoubleParser/fastdoubleparser-dev/src/main/java/ch.randelshofer.fastdoubleparser/ch/randelshofer/fastdoubleparser/JavaBigDecimalFromCharArray.java

Line 305 in 0a5ca6a

fractionalPart = ParseDigitsTaskCharArray.parseDigitsRecursive(str, decimalPointIndex + 1, exponentIndicatorIndex, null);

The ParseDigitsTaskCharArray.parseDigitsRecursive method cannot handle null values for this param.

Edit: I have changed the code in this PR to call ParseDigitsTaskCharArray.parseDigitsInteractive instead.

[wrandelshofer]

Thank you very much for this pull request.
Unfortunately the suggested fix is incomplete.
We have to replace all calls to parseDigitsRecursive with last argument null by calls to parseDigitsIterative.
I am going to fix this.

[pjfanning]

Thanks @wrandelshofer - I added an extra commit but feel free to ignore this PR and look at your own fix.

[wrandelshofer]

I have fixed it know. The fix is in the main branch.
The main branch should be good for use in rev 6080865

[cowtowncoder]

Thank you @wrandelshofer for such a quick fix!