Feat/WPB-18240 handle MLS HTTP exceptions

[MarianKijewski]

---

PR Submission Checklist for internal contributors

• The PR Title

  • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • contains a reference JIRA issue number like SQPIT-764
  • answers the question: If merged, this PR will: ... ³

• The PR Description

  • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

---

What's new in this PR?

Issues

Not possible to specify exactly what HTTP exception indicates

Causes

Standard exceptions were mapped into custom Wire exception without exposing additional information

Solutions

• Map error response to serialized data class that holds label of the exception using native Ktor HTTP response validator
• Remove custom mapper

Testing

Test Coverage

• I have added automated test to this contribution

---

PR Post Submission Checklist for internal contributors (Optional)

• Wire's Github Workflow has automatically linked the PR to a JIRA issue

---

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

[alexandreferris]

Great work! I just added some nitpick comments but overall super great! now we have better handling of exceptions 🙌🏻

[Copilot]

Pull Request Overview

This PR refactors HTTP exception handling to provide more specific error information, particularly for MLS (Message Layer Security) HTTP exceptions. The changes replace a generic exception mapping approach with a structured response validator that can identify specific error types through response labels.

Key changes:

• Implemented native Ktor HTTP response validation for better error handling granularity
• Added structured error response mapping with label-based exception identification
• Replaced generic HTTP status code checking with specific label-based exception detection for MLS stale message errors

Reviewed Changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
WireExceptionMapperTest.kt	Removed old generic exception mapping tests
HttpClientExceptionTest.kt	Added comprehensive tests for new HTTP response validation with MLS-specific error scenarios
WireApplicationManager.kt	Updated to use label-based MLS stale message detection instead of HTTP status code
ErrorResponse.kt	New data class for structured error response parsing
WireExceptionMapper.kt	Refactored to handle Ktor ResponseException with structured error response parsing
WireException.kt	Updated ClientError and InternalSystemError to use ErrorResponse with MLS-specific helper methods
NetworkErrorLabel.kt	Added constants for network error labels
Modules.kt	Integrated new HTTP response validator into HttpClient configuration
BackendClientImpl.kt	Removed generic exception wrapper calls
BackendClientDemo.kt	Removed generic exception wrapper calls and updated exception handling

[Copilot]

Function name contains a spelling error: 'Unknow' should be 'Unknown'

Suggested change

	fun whenErrorResponseDoesNotContainLabelThenThrowUnknowException() {
	fun whenErrorResponseDoesNotContainLabelThenThrowUnknownException() {

[Copilot]

The function returns Unit but always throws an exception. Consider changing the return type to Nothing to make the non-returning behavior explicit

Suggested change

	suspend fun Throwable.mapToWireException() {
	suspend fun Throwable.mapToWireException(): Nothing {

[Copilot]

Consider logging the JsonConvertException before falling back to UnknownError to aid in debugging serialization issues

Suggested change

	} catch (_: JsonConvertException) {
	} catch (e: JsonConvertException) {
	logger.error("JsonConvertException occurred while processing the response: ${e.message}", e)