feat: 500+ error handling

[tom-laplace]

🔗 Linked issue

Issue : #3

It's not an open issue but as I was reading the comments you seems interested in this changes.

❓ Type of change

• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Resolves : #3

Context

Currently, requests that receive 500+ status codes throw an error instead of returning an ApiResponse object.
This makes it difficult to test and handle server errors in a consistent way.

Changes

• Modified error handling to treat 500+ errors like other HTTP errors
• All HTTP errors now return an ApiResponse object
• Added tests for server error handling

Benefits

• Consistent error handling across all HTTP status codes
• Easier testing of server error scenarios

Breaking Changes

• Requests that receive 500+ status codes no longer throw errors
• Code that was catching 500+ errors will need to check response.hasFatalError() instead

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

I am ready to open a PR on the doc if this one is merged.
It's my first "real"' open-source PR, feel free to point out any mistakes or improvements I can make to it 😄

[thetutlage]

Thanks 👍