Allow FilteringParserDelegate to skip last elements in array

[pgomulka]

FilteringParserDelegate when parsing ID_END_ARRAY or ID_END_OBJECT of the skipped element (when _headContext.isStartHandled() == false should be able to exit the loop and continue parsing next tokens.

This logic was changed accidentally removed in 7db467d#diff-f6642caef61e0c403f51a6150ecf45263034fca5002782fd02eacd01e53fe549L694

closes #882

[cowtowncoder]

Ok, one quick question first: would it make sense to rebase against 2.14 instead of 2.15, or would this be too risky a change? It seems like it might be safe for a patch, and that way would be released earlier (2.15.0 is still bit out).
I am fine either way.

Also: before merging I'd need CLA (unless I have received one before -- apologies if I missed it).

CLA is from here: https://github.com/FasterXML/jackson/blob/master/contributor-agreement.pdf
(and there is also alternative Corporate CLA that is sometimes used although most contributions are with individual CLA).

The usual way is to print the doc, fill & sign, scan/photo, email to info at fasterxml dot com.
Once I receive it I can merge this to whichever branch we want (I can also merge it to 2.15 and cherry-pick in 2.14 if necessary).

Thank you again for contributing this -- looking forward to merging it ASAP!

[tvernum]

@cowtowncoder I believe you have a corporate CLA for Elastic.
I'll arrange to have @pgomulka and I added to schedule A.

[pgomulka]

Ok, one quick question first: would it make sense to rebase against 2.14 instead of 2.15, or would this be too risky a change? It seems like it might be safe for a patch, and that way would be released earlier (2.15.0 is still bit out).

@cowtowncoder I can either rebase this PR against 2.14 and forward-port it to 2.15
or we could backport this commit to 2.14 after it is merged to 2.15.

What is the preferred way in fasterxml project?

[pjfanning]

target 2.14 and then we'll merge to 2.15 and master

[cowtowncoder]

@cowtowncoder I believe you have a corporate CLA for Elastic. I'll arrange to have @pgomulka and I added to schedule A.

I had a feeling I should have CCLA for Elastic but for some reason I don't seem to be able to locate it.
If you could send an updated version (with schedule A list) I'll make sure to check this into repository.

[cowtowncoder]

Given that there should be CLA in effect & there will be updated one sent, I will merge this now.