Throw proper exception when request parsing fails

還沒有人認領這個 Issue。

Currently calling the .body method (or injecting it) and sending invalid content to the endpoint throws a generic java.text.ParseException or MapperWrongTypeException from abstract-data. The stacktrace is hard to debug since it doesn't contain any context (endpoint, invalid data, etc.)

Instead we should throw an exception that contains more context and can be properly handled in the exception handler and responded to.

1. Invalid request body throws a specific exception
2. The default exception handler, responds with 400

從 .body 方法或 body 注入所使用的請求解析路徑開始，接著追蹤 ParseException 和 MapperWrongTypeException 如何到達預設例外處理器。為請求本文失敗加入上下文，並驗證無效請求本文會產生特定例外和 400 回應。

由索引模型根據 Issue 內容生成。