feat: docsgpt up --native

Run DocsGPT without Docker: the API and the worker each become a service
on the machine itself, a launchd agent on macOS and a systemd user unit
on Linux, pointed at a PostgreSQL and a Redis that already run.

`docsgpt up --native --postgres-uri ... --redis-url ...` writes the same
.env a Docker install uses, applies the migrations and starts both
services. status, logs, down and uninstall work on a native install the
same way they do on a Docker one, and never touch the database or Redis:
they were the user's to begin with.

One Redis URL covers the broker, the result backend and the cache on
three consecutive databases, starting at the one the URL names, so a
Redis that already holds something else can be shared.

Windows has neither service manager, so native mode refuses it and says
what to do instead.

.github/styles/config/vocabularies/DocsGPT/accept.txt

@@ -3,9 +3,9 @@ Anthropic's
 api
 APIs
 Atlassian
-automations
 autoescaping
 Autoescaping
+automations
 backfill
 backfills
 bool
@@ -21,9 +21,9 @@ diarization
 Docling
 docsgpt
 docstrings
+enqueues
 Entra
 env
-enqueues
 EOL
 ESLint
 feedbacks
@@ -35,6 +35,7 @@ hardcoding
 Idempotency
 JSONPath
 kubectl
+launchd
 Lightsail
 llama_cpp
 llm
@@ -70,6 +71,7 @@ SGLang
 Shareability
 Signup
 Supabase
+systemd
 UIs
 uncomment
 URl