[Bug]: setup.sh calls docker-compose instead of docker compose

[gander]

Description
Setup script fails at the last step because it invokes the legacy docker-compose binary directly instead of the docker compose plugin syntax. The prerequisite check earlier in the same run confirms Docker Compose is detected, but that check apparently only verifies the docker compose plugin, not the standalone docker-compose command that the script later shells out to.

Steps to reproduce

1. Run the install script: curl -fsSL https://raw.githubusercontent.com/orneryd/Mimir/main/install.sh | bash
2. Let it clone the repo and run setup.sh
3. Wait for it to reach the "Starting Docker services" step

Expected behavior
Docker services start using the detected Docker Compose installation (docker compose ...).

Actual behavior
Script fails with:

./scripts/setup.sh: line 418: docker-compose: command not found

even though the prerequisite check earlier reported:

[SUCCESS] Docker Compose detected

Environment

• OS / platform: Linux
• Version / tag: Node.js 24.18.0, npm 11.16.0, Docker 29.6.1, Git 2.43.0
• Browser (if applicable): n/a
• Relevant config: Docker Compose v2 plugin installed (no standalone docker-compose v1 binary on PATH)

Logs / screenshots

[INFO] Starting Docker services...
[INFO] Embeddings disabled - skipping Ollama service
./scripts/setup.sh: line 418: docker-compose: command not found

Proposed solution
Replace hardcoded docker-compose calls in setup.sh (line 418 and any similar spots) with docker compose, or detect which one is available and use that.

Two side notes surfaced in the same run that may be worth separate issues:

1. Copilot API proxy failed to start and the LLM connection test failed, requiring manual copilot-api start and re-authentication.
2. npm install reports 43 vulnerabilities (2 low, 17 moderate, 22 high, 2 critical) in the dependency tree.