Improve Error Handling Architecture

[Ezequiel-Valencia]

Introduce a flow which allows for errors to be logged, have their appropriate HTTP codes, and be included within the generated OpenAPI spec.

• Introduce VCellHTTPError response object for errors
• Ensure each endpoint throws the appropriate error that is expected
• Utilize a factory method within the client to de-marshal the errors thrown by the server, while keeping the original function signatures
• Unit tests for error handling.

[Ezequiel-Valencia]

In total this PR provides the following changes:

• Update Quarkus server error handling architecture such that:
  • All errors thrown from handlers are web based errors, that is they inherit the base error ApiException
  • Exception mappers are used to catch all exceptions and return to the client an appropriate response
  • Logging all errors on the server that are thrown back to the client
• Utilize an error factory in the GUI client that assigns web errors to domain specific errors
• Remove git patches that fixed client file receiving, now implementing fixes within the custom object mapper

[Ezequiel-Valencia]

• Relocate the custom object mapper
• Ensure all original server errors are preserved when sending errors to the client, such that they can see the same message and catch the same exception
• Remove the hard coded BioModel error used for testing.

[jcschaff]

This was great work. we now have a good pattern for migrating the endpoints from RPC to REST while preserving error handling. Approved.