No easy way to configure Colima to use the default Docker socket

### Description

On my work mac I was trying Colima, and had to remove my old Docker Desktop socket and symlink Colima's socket - the issue & fix are documented [here](https://github.com/abiosoft/colima/issues/71#issuecomment-1048749674). My docker socket clash was also from testcontainers.

On my personal mac I was trying `act` to run GitHub Actions locally, and got
```
ERRO[0000] failed to obtain container engine info: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
...
Error: Error occurred running finally: Error occurred running finally: failed to list containers: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? (original error: ) (original error: unable to determine if image already exists for image 'ghcr.io/catthehacker/ubuntu:act-latest' (): Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?)
```

So I'm 2 for 2 on needing to delete the old socket and symlink Colima's.
It seems very common for tools to point to that socket file.

My feature request is that it'd be great if Colima would either 1. _just make it work_ on installation, or prompt and suggest to let it do the fix for you. Actually, is it even worth asking?

If we can remove this snagging point, it'd make the early user experience a lot smoother. The project descripition is after all:

> Container runtimes on macOS (and Linux) with _minimal setup_

I've had no other issues/requests so far - it's been working great for a few days!