fix: mount Docker socket in devcontainer to fix bazel run (#248) (#258)

* fix: mount Docker socket in devcontainer to fix bazel run

Fixes #248

When running  inside the
devcontainer, the generated run_docker.sh script calls
and . These fail because the host Docker socket
(/var/run/docker.sock) was not mounted into the container, resulting in:

  failed to connect to the docker API at unix:///var/run/docker.sock;
  dial unix /var/run/docker.sock: connect: no such file or directory

Add a bind mount for the Docker socket in .devcontainer/devcontainer.json
so that Docker commands inside the devcontainer communicate with the
host Docker daemon.

* Fix Formatting

---------

Co-authored-by: akshaylg0314 <akshay14.garg@lge.com>

Author: akshaylg0314

.devcontainer/devcontainer.json

@@ -1,6 +1,9 @@
 {
-    "name": "eclipse-s-core",
-    "image": "ghcr.io/eclipse-score/devcontainer:v1.3.0",
-    "postCreateCommand": "bash .devcontainer/prepare_workspace.sh",
-    "postStartCommand": "ssh-keygen -f '/home/vscode/.ssh/known_hosts' -R '[localhost]:2222' || true"
+  "name": "eclipse-s-core",
+  "image": "ghcr.io/eclipse-score/devcontainer:v1.3.0",
+  "mounts": [
+    "source=/var/run/docker.sock,target=/var/run/docker.sock,type=bind"
+  ],
+  "postCreateCommand": "bash .devcontainer/prepare_workspace.sh",
+  "postStartCommand": "ssh-keygen -f '/home/vscode/.ssh/known_hosts' -R '[localhost]:2222' || true"
 }