Stabilize `twoliter` CLI, deprecate `twoliter make`

Twoliter has stabilized its core build functionality behind a CLI that should treat as semantically stable (`twoliter build`, `twoliter update`, `twoliter publish`, `twoliter fetch`).

On the other hand, many build system features still lean on the legacy "cargo-make" interface exposed via `twoliter make`.

This issue is meant to track the stabilization of these commands behind CLI interfaces. Eventually, we should drop `twoliter make` after we feel that the relevant behaviors are properly exposed.

To get a sense of which interfaces should be considered for extraction, you can look at the [`Makefile` in `bottlerocket-os/bottlerocket`](https://github.com/bottlerocket-os/bottlerocket/blob/562219f94afba45b06305f5bb971e5600f687497/Makefile.toml#L293). Any task of the following form will need attention:

```
[tasks.TASK_NAME]
run_task = "run-twoliter"
```

Start by reviewing the linked Bottlerocket Makefile and identify each task using run-twoliter. Determine which legacy twoliter make behaviors need stable CLI interfaces; the work is done when the relevant behaviors are exposed and twoliter make can eventually be removed.

Written by the indexing model from the issue text.