planning: Cortex CLI should be a layer on top of the API Server

[vansangpfiev]

Sub-ticket from Epic: #1415

Problem Statement

Cortex CLI does not use the API Server in all commands

Feature Idea

Cortex CLI should be a layer on top of the API Server.
This is quite straight forward except for cortex pull and cortex engines install.
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 (will need websockets to track download progress).
Related ticket: #1423

For cortex pull and cortex engines install using API server, can we move them into v1.0.2 instead of v1.0.1?

cc: @dan-homebrew @0xSage @gabrielle-ong @namchuai @nguyenhoangthuan99

[vansangpfiev]

Another thing: because CLI is a layer on top of the API server, CLI will start the Server if it is not started, before executing any command.

[gabrielle-ong]

Marking as complete, as a subtask under #1415