chore: harmonize error handling

[ClemDoum]

PR description

Harmonize error handling in order to:

• log normalized messages
• return normalized HTTP errors
• avoid returning traces containing potential logs in http responses

Changes

datashare-neo4j-extension/src

Changed

• udpated HttpError to avoid deserializing the trace attribute, this way no trace information will be returned by the HTTP. In order to be able to log message with traces a HttpError.getMessageWithTrace() method was added
• removed inheritance between Neo4jAppError and HttpError to isolate their behavior. Neo4jAppError represents a error returned by the Python application, it serialization had not reason to be bound to the HttpError serialization/deserialization
• improved Java error handling by catching error locally and throwing detailed RuntimeError
• refactored wrapNeo4jAppCall to reformat any unhandled exception into the HttpError using HttpError.fromException which converts any exception in a single format. The wrapper logs error with trace and return HTTP errors without traces
• refactored all API routes to be fully wrapped into the wrapNeo4jAppCall, the deserialization of the incoming payload is done using the parseContext function which raise a custom BadRequest error which it later caught and reformatted into the HttpError. This allows to return normalized errors in case of a 400 error rather than retuning the non formatted error from fluent

datashare-neo4j-extension/pom.xml

Fixed

• include test files in the files checked using ./neo4j format_test_java and updated java files accordingly

[ClemDoum]

Thanks for the review @pirhoo