epic: `cortex pull` and `cortex engines install` CLI uses API server

[gabrielle-ong]

Problem

• cortex pull and cortex engines install require additional thought to separate CLI and API.
• We use libcurl UI/UX for download progress for above CLI commands and get the models, engines directly from Github, HF, ... - The execution via /v1/models/pull and /v1/engines/install requires a lot of changes in UI/UX and logic
• we will need websockets to track download progress (done) - feat: Model Pull has clear API and CLI to support Huggingface Repos #1242

Related tickets:

• epic: Cortex has a better CLI UI for downloading #1423
• followup task from planning: Cortex CLI should be a layer on top of the API Server #1492
• followup task from epic: Separate CLI and API processes #1415

Tasklist

• [ ]

Success Criteria

[gabrielle-ong]

QA ✅
Cortex-nightly v222

cortex pull and cortex engines CLI commands use API server