[BUG] flytectl demo start fails on Mac when using Docker Desktop

### Describe the bug

It seems flyectl demo fails to use default Docker configuration.

```
brew install flyteorg/homebrew-tap/flytectl (worked)
% flytectl demo start
INFO[0000] [0] Couldn't find a config file []. Relying on env vars and pflags.
🧑‍🏭 Bootstrapping a brand new Flyte cluster... 🔨 🔧
Error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
{"json":{},"level":"error","msg":"Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?","ts":"2025-01-03T23:09:33-08:00"}
```

```
% docker ps | head -2
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ccd36f830cc9 5ddc6458eb95 "/metrics-server --c…" 42 minutes ago Up 42 minutes k8s_metrics-server_metrics-server-86776f5749-qmp8c_kube-system_e9f65542-d8fc-43b7-9956-d22a6cf6ef98_6
```

### Expected behavior

I was expecting the demo to start. It seems straightforward (the issue), but I tried to look for relating settings and so far have not succeeded. I thought I would find something to change the Docker sock address.

```
% docker info | grep address
WARNING: daemon is not using the default seccomp profile
com.docker.desktop.address=unix:///Users/me/Library/Containers/com.docker.docker/Data/docker-cli.sock
```

### Additional context to reproduce

```
brew install flyteorg/homebrew-tap/flytectl
flytectl demo start
```

### Screenshots

_No response_

### Are you sure this issue hasn't been raised already?

- [X] Yes

### Have you read the Code of Conduct?

- [X] Yes

Start by reproducing `flytectl demo start` on macOS with Docker Desktop and compare its Docker socket configuration with the address reported by `docker info`. Trace the demo startup entry point that creates the Flyte cluster; done means the command connects to Docker Desktop and starts the demo successfully.

Written by the indexing model from the issue text.