v2.1.1 — Local commands cost no API budget

🐛 Fix: local commands no longer consume cloud API quota

Command throttling and API-quota accounting used to run in the shared command-retry engine, before the local/cloud routing decision — so a command carried over the local gateway still counted against the monthly cloud budget, and (worse) was blocked when that budget was exhausted.

Now throttling + quota accounting apply to the cloud path only:

• A command routed locally consumes no quota, is not rate-limited, and works even with an exhausted cloud budget.
• Cloud commands still count exactly once per attempt (retries included).
• The Automower path is unchanged.

Local state/monitoring never used cloud quota; this closes the gap for local commands too.

Requires local gateway access (v2.1.0) to be enabled — see that release for setup.

Quality

736 tests · 100% coverage · mypy --strict clean · ruff clean.

See #45 for the full change.