Pick status code from ErrorResponse interfaces

[buttilda]

Unhandled exceptions that extend spring-boot's ErrorResponse have a status code defined and we should use that instead of forcing it to be 500

Description

Adding problem-spring-web to your project has a consequence of turning exceptions which haven't been explicitly handled into 500s. While at face value this may seem like a reasonable default behaviour, one should take into consideration that spring-boot can throw errors internally which have status codes attached to them, so it's only fair that problem should listen to those and pass them forwards.

Motivation and Context

Adding problem-spring-web to a bare spring-boot project and extending from ProblemHandling causes errors to turn into 500s. For example, calling an endpoint that doesn't exist results in 500 Resource not found instead of 404 Resource not found which is the default and expected behaviour.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.

[MALPI]

👍