oma CLI envs get and delete

oma envs get <id> hits GET /v1/environments/:id and prints name/id/type plus optional sandbox provider, harness, status, kind, description, and created date; --json emits the raw object. oma envs delete <id> hits DELETE /v1/environments/:id; 409 (active sessions) and 404 surface through apiFetch; empty delete bodies still honor --json envelopes (see project-oma-cli-empty-2xx).

Why: Smoke and ops need read-back and cleanup of environments without raw oma api calls; #484 item 5.

How to apply: Shipped on tip 56d682e1 via #488 + Version Packages #490; npm @getoma/[email protected] published (Release 37071142257). Soft CLI QA: oma --version (0.1.14), oma envs get --help, oma envs delete --help, then live get/delete against a disposable env id. #484 remains open for envs create config, oma usage, and hosted runtime list.