Destination Hasura URL forced to IPv4 (#346)

Similar to #343 but for the docker extension

docker-extension/README.md

@@ -4,7 +4,7 @@ See Docker extension SDK, especially the UI and VM sections of the metadata.
 * The difference between the docker-compose files is the metabase image used.
 * The docker-compose files are copies of the original one with all parameters set. It is not possible to easily pass environment variables to the extension.
 
-## Installation
+## Installation (for dev purposes)
 
 1. Build Docker image
 
@@ -24,6 +24,12 @@ See Docker extension SDK, especially the UI and VM sections of the metadata.
   docker extension rm farosai/faros-ce-docker-extension:latest
   ```
 
+## Publishing (Faros-only)
+
+```shell
+make push-extension TAG=X.Y.Z
+```
+
 ## Further reading
 Docker extension SDK, especially the UI and VM sections of the metadata
 We use different docker-compose files 

docker-extension/docker-compose_amd64.yaml

@@ -16,7 +16,7 @@ services:
       - faros-db
     environment:
       AIRBYTE_API_CALLS_CONCURRENCY:
-      AIRBYTE_DESTINATION_HASURA_URL: "http://localhost:8080"
+      AIRBYTE_DESTINATION_HASURA_URL: "http://127.0.0.1:8080"
       AIRBYTE_FORCE_SETUP: false
       AIRBYTE_URL: "http://airbyte-webapp:80"
       FAROS_EMAIL:

docker-extension/docker-compose_arm64.yaml

@@ -16,7 +16,7 @@ services:
       - faros-db
     environment:
       AIRBYTE_API_CALLS_CONCURRENCY:
-      AIRBYTE_DESTINATION_HASURA_URL: "http://localhost:8080"
+      AIRBYTE_DESTINATION_HASURA_URL: "http://127.0.0.1:8080"
       AIRBYTE_FORCE_SETUP: false
       AIRBYTE_URL: "http://airbyte-webapp:80"
       FAROS_EMAIL: