Adjust Exception Behaviour during BPMN, CMMN, Decision Parsing

[psavidis]

Acceptance Criteria (Required on creation)

As a User of the Java & REST API, i want the parsing of the different deployable resources to be consistent in the case of missing HistoryTimeToLive.

Hints

• Currently, BPMN Parse exceptions will be handled as 400 error response (BAD_REQUEST)
• Cases & Definition Parse exceptions are wrapped into a ProcessEngineException which in turn is handled with a 500 error response code. It should be 400.
• We need to Design how this exception handling is going to be achieved in favour of the API.

Links

• https://github.com/camunda/camunda-bpm-platform/issues/2994

Breakdown

### Pull Requests

Dev2QA handover

• [ ] Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

[tasso94]

Hi @psavidis, Thanks for raising this problem.

Since this behavior did not change with your code changes, i.e., a TTL with a not-allowed value led to the same error behavior in the past, I would keep everything as it is and wait for user feedback. We could potentially address this after collecting more evidence that this is really a problem.