Follows Go naming conventions where the package name already
provides context, so daemon.New reads better than
daemon.NewDaemonCmd.

Extract a composeCmd helper in the docker compose manager to
eliminate duplicated exec.Cmd construction across Start, down,
and isContainerRunning. This also fixes a subtle inconsistency
where down and isContainerRunning were using the raw ComposeYAML
instead of the patched output from getComposeYAML.

Remove the IsRunning guards from the start and stop subcommands
since docker compose up and down are idempotent operations. The
guards introduced a TOCTOU race without adding value.

We now use a GOTESTSUM variable across unit, integration, and e2e test targets so
we can override the command path in different environments without editing the
Makefile each time.

This brings the e2e harness in line with the explicit daemon lifecycle behavior
and removes backend-specific assumptions from shared tests.

Previously, docker e2e targets depended on compose setup while k8s tests still
assumed localhost URLs. That caused drift and failures when running against
Kind load balancer endpoints.

Now, docker e2e starts and purges through arctl daemon commands, k8s discovers
the registry LoadBalancer URL at runtime, and daemon startup always pulls the
latest configured image tag.

This prevents local-only CLI commands from failing due to registry connectivity checks
and keeps command behavior aligned with explicit daemon control.

Previously, root pre-run setup still ran for local commands and completion
flows, so commands like completion, build, and version could fail with
connection errors when the daemon was not running.

Now, those command paths are explicitly skipped in pre-run setup, tests cover
the skip matrix, and version falls back to a direct client so --json still
works when pre-run initialization is bypassed.

This updates user and governance docs to reflect the explicit daemon controls.

The docs now direct users to run arctl daemon start before registry commands,
and they call out rerunning daemon start after upgrading the CLI.

This keeps the e2e target readable by moving daemon lifecycle actions into
explicit helper targets.

Now test-e2e-docker depends on daemon-start and uses daemon-stop-purge in its
EXIT trap, so the command flow is clearer and easier to maintain.

This consolidates local lifecycle management around daemon commands and
keeps the CLI path configurable.

run-docker and down now call daemon targets, docker-compose helper targets are
removed, and daemon helper commands use ARCTL with a default of ./bin/arctl.

This keeps the quick reference in sync with the Makefile lifecycle changes
by pointing to daemon-start and daemon-stop instead of removed compose targets.

This keeps the fallback note but shortens the wording around the version
client initialization path when root pre-run is skipped.

Signed-off-by: timflannagan <[email protected]>

This makes backend intent explicit in deploy e2e tests and removes repeated
string checks spread across multiple cases.

The local-only lifecycle test is now named accordingly, unsupported targets are
skipped through a shared helper, and target constants make local versus
kubernetes behavior easier to read and maintain.