docs: Version docs for v3.0.4 [skip ci]

Author: apify-service-account

website/versioned_docs/version-3.0/02_concepts/04_error_handling.mdx

@@ -19,7 +19,7 @@ When you use the Apify client, it automatically extracts all relevant data from
 The Apify client provides dedicated error subclasses based on the HTTP status code of the failed response, so you can branch on error kind without inspecting `status_code` or `type`:
 
 | Status | Subclass |
-|---|---|
+| --- | --- |
 | 400 | <ApiLink to="class/InvalidRequestError">`InvalidRequestError`</ApiLink> |
 | 401 | <ApiLink to="class/UnauthorizedError">`UnauthorizedError`</ApiLink> |
 | 403 | <ApiLink to="class/ForbiddenError">`ForbiddenError`</ApiLink> |

website/versioned_docs/version-3.0/02_concepts/10_custom_http_clients.mdx

@@ -78,7 +78,7 @@ It must return an object satisfying the <ApiLink to="class/HttpResponse">`HttpRe
 <ApiLink to="class/HttpResponse">`HttpResponse`</ApiLink> is not a concrete class. Any object with the following attributes and methods will work:
 
 | Property / Method | Description |
-|---|---|
+| --- | --- |
 | `status_code: int` | HTTP status code |
 | `text: str` | Response body as text |
 | `content: bytes` | Raw response body |

website/versioned_docs/version-3.0/02_concepts/11_timeouts.mdx

@@ -15,7 +15,7 @@ import TimeoutsSyncExample from '!!raw-loader!./code/11_timeouts_sync.py';
 The Apify client uses a tiered timeout system to set appropriate time limits for different types of API requests. Each tier has a default value suited to its use case:
 
 | Tier | Default | Purpose |
-|---|---|---|
+| --- | --- | --- |
 | `short` | 5 seconds | Fast CRUD operations (get, update, delete) |
 | `medium` | 30 seconds | Batch, list, and data transfer operations |
 | `long` | 360 seconds | Long-polling, streaming, and heavy operations |