Handle JsonParseException

[lassetyr]

Adds handling of JsonParseException - now returns a 400 Bad Request.

This typically occurs when GraphQL-requests contain malformed JSON.

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (acd912d) 64.79% compared to head (aabf4eb) 64.80%.

Additional details and impacted files

@@            Coverage Diff             @@
##             dev-2.x    #5121   +/-   ##
==========================================
  Coverage      64.79%   64.80%           
- Complexity     14160    14164    +4     
==========================================
  Files           1733     1733           
  Lines          67487    67498   +11     
  Branches        7221     7223    +2     
==========================================
+ Hits           43729    43739   +10     
  Misses         21330    21330           
- Partials        2428     2429    +1     

Impacted Files	Coverage Δ
...opentripplanner/api/common/OTPExceptionMapper.java	0.00% <0.00%> (ø)
...pplanner/graph_builder/module/osm/OsmDatabase.java	78.57% <0.00%> (-0.77%)	⬇️

... and 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[vpaturet]

Tested with:
{ "query" : "{stopPlace(id:"NSR:StopPlace:17099"){id name estimatedCalls(timeRange:72100 numberOfDepartures:10){realtime aimedArrivalTime aimedDepartureTime expectedArrivalTime expectedDepartureTime destinationDisplay{frontText}}}}" }

I got a warning in the log:
WARN (GraphQL.java:493) Query did not parse : '{ "query" : "{stopPlace(id:"NSR:StopPlace:17099"){id name estimatedCalls(timeRange:72100 numberOfDepartures:10){realtime aimedArrivalTime aimedDepartureTime expectedArrivalTime expectedDepartureTime destinationDisplay{frontText}}}}" }'

but the return code is still 200 with the following GraphQL response:

{
  "errors": [
    {
      "message": "Invalid syntax with offending token '\"query\"' at line 1 column 3",
      "locations": [
        {
          "line": 1,
          "column": 3
        }
      ],
      "extensions": {
        "classification": "InvalidSyntax"
      }
    }
  ]
}

[lassetyr]

JsonParseException is thrown when Content-Type-header is set to application/json

[vpaturet]

Ok, so this PR covers the case when a request is sent with the content type "application/json" and the content is invalid JSON. In this case the client gets an HTTP 400 status.
If the content type is "application/graphql" and the content is invalid GraphQL, the client gets an HTTP 200 status with error nodes in the response.