Fix a crash & add ftest to cover other reported cases

[fgalan]

This PR:

• Provides a fix (a covering ftest) for issue Possible Illegal read memory access in APIv2 when sending malformed request #3603
• Provides covering ftests for issues Possible stack-overflow in APIv2 in rapidJson dependency when sending deeply nested request #3604, Possible stack overflow in APIv2 in CompoundValueNode.cpp when sending nested request #3605, Possible stack-overflow in APIv2 in parseContextAttributeCompoundValue.cpp when sending large but valid requests #3606 and Another possible stack overflow in APIv1 in boost jsonParser dependency #3608. In this case, we haven't been able to reproduce the case (so no fix is needed), but a test is included to cover the reported cases.
• Would be expanded with nex fixes and/or ftests when Possible stack overflow in APIv1 in boost jsonParser dependency #3607 and Possible illegal read access on zero page in APIv1 in StatusCode.cpp #3609 gets clarified (some questions has been done in the referred issued). That's why it's now in WIP status.

@0xricksanchez it would be great if you could have a look to the .test in this PR to ensure they cover the cases you reported in the issues, pls. Thanks!

[fgalan]

@0xricksanchez it would be great if you could have a look to the .test in this PR to ensure they cover the cases you reported in the issues, pls. Thanks!

Did you have a chance to do the checking, please?

Thanks!

[fgalan]

• Would be expanded with nex fixes and/or ftests when Possible stack overflow in APIv1 in boost jsonParser dependency #3607 and Possible illegal read access on zero page in APIv1 in StatusCode.cpp #3609 gets clarified (some questions has been done in the referred issued). That's why it's now in WIP status.

Update: with regards to #3607 this new commit caeb5dd adds a test case covering the cases (test/functionalTest/cases/3607_killer_request_apiv1/killer_request_apiv1_parsing_cases.test). As you can see, I'm being unable to reproduce the crash based in the inputs provided in that issue and what I get for each one of the three requests is an NGSI-v1 style error message:

{
    "errorCode": {
        "code": "400",
        "details": "JSON Parse Error",
        "reasonPhrase": "Bad Request"
    }
}

Mabye something is wrong in the added .test? It would be great if @0xricksanchez could have a look please?

With regards to the other issue, I'm still waiting for clarification, see #3609 (comment)

[fgalan]

Recent commits in 9d8775d and fbb27c4 implement and maximum nesting limit (50 levels) so the 500 Internal Error due to MongoDB error is now transformed in a 400 Bad Request message with informative message.

[AlvaroVega]

LGTM

[fgalan]

@fisuda this PR includes a small addition to one of the .md documentation files. It would be great if you could sync the Japanese translation. Thanks!

[fisuda]

Noted with thanks!