feat(api)!: register missing exceptions and consolidate error builders

[etiennej70]

PR Description

What this PR Provides

• Enable Spring Boot native Problem Details handling with spring.mvc.problemdetails.enabled=true.
• Refactor the central API exception handler to return RFC 7807 / RFC 9457 ProblemDetail responses.
• Keep the domain layer HTTP-agnostic by centralizing exception-to-status mapping in infrastructure.
• Update Swagger/OpenAPI responses to document the real error contract with ProblemDetail.
• Refresh integration tests and the published docs/src/static/swagger.yaml to match the new error format.

Review

The reviewer must double-check these points:

• The reviewer has tested the feature
• The reviewer has reviewed the implementation of the feature
• The documentation has been updated
• The feature implementation respects the Technical Doc / ADR previously produced
• The Pull Request title has a ! after the type/scope to identify the breaking change in the release note and ensure we will release a major version.

How to test

Please refer (copy/paste) the test section from the User Story. This should include

• The initial state: the project runs with the local profile and a PostgreSQL database available.
• What and how to test: trigger validation, not-found, conflict, unauthorized, and unprocessable-content API errors through the REST endpoints.
• Expected results: error responses return application/problem+json with RFC 7807 fields (type, title, status, detail, instance), and Swagger documents those responses with ProblemDetail.

Breaking changes (if any)

• API JSON schema modification (existing resource / behavior)
• Behavior modification of a component
• Others

Context of the Breaking Change

The API error contract moved from the custom {error, error_description} shape to Spring's native Problem Details format.

Result of the Breaking Change

API consumers must read RFC 7807 fields from application/problem+json responses instead of the old custom error payload.

[sonarqubecloud]

Quality Gate passed

Issues
7 New issues
0 Accepted issues

Measures
0 Security Hotspots
94.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-code-quality]

Code Coverage Overview

Languages: Java

Java / code-coverage/jacoco

The overall coverage in commit a26e858 in the feat/error_messages branch remains at 91%, unchanged from commit 8dfc367 in the main branch.

Show a code coverage summary of the most impacted files.

File	main 8dfc367	feat/error_messages a26e858	+/-
com/decathlon/i...ionHandler.java	83%	94%	+11%