fix: enhance error handling for network and server errors in retry logic

[egalvis27]

What is Changed / Added

• Updated Drive client error mapping to classify transport-level failures without an HTTP response/status as NETWORK_ERROR.
• Updated folder creation error mapping so NETWORK_ERROR is treated as transient and routed through the same retry path as server-side transient failures.
• Validated the change with focused tests for interceptor/client behavior and folder creation flow.

Why

• When copying folders from the file manager, mkdir could fail on the first attempt and then succeed on manual retry.
• Logs showed the underlying cause was a transport timeout (for example ETIMEDOUT) on POST /folders, meaning a network failure with no HTTP status.
• Previously, this scenario was not handled as a transient retryable error in the folder creation flow, so it surfaced as a final user-facing failure.
• With this change, status-less network failures are retried automatically, reducing intermittent folder creation/upload failures and improving user experience.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud