[autodev] Update Jetson test environment and satellite-provider integration

- Added `.env.test` to `.gitignore` to exclude test environment variables.
- Enhanced `docker-compose.test.jetson.yml` to include the real satellite-provider .NET service and its PostgreSQL database, replacing the mock service.
- Updated test execution policy to mandate all tests run exclusively on Jetson hardware, deprecating the previous two-tier model.
- Revised documentation in `_docs/LESSONS.md`, `_docs/02_document/tests/environment.md`, and `_docs/04_deploy/ci_cd_pipeline.md` to reflect the new testing strategy and environment setup.
- Improved `run-tests-jetson.sh` script to ensure proper environment variable handling and satellite-provider integration.

This commit aligns the testing framework with production environments, enhancing reliability and coverage.

_docs/04_deploy/ci_cd_pipeline.md

@@ -9,6 +9,16 @@
 > is now stale and will be reconciled in autodev's existing-code Step 13
 > (Update Docs); the operative CI contract is here.
 
+> **Test-execution policy — 2026-05-20**: all tests run on the Jetson
+> (colocated arm64 Woodpecker agent) only. The historical "Tier-1
+> workstation Docker" path is deprecated. The `companion-tier1` and
+> `operator-orchestrator` images below are still built and pushed for
+> registry distribution (operator workstations consume the operator
+> image; the cycle-2 `companion-jetson` image is the planned successor
+> to `companion-tier1`), but no x86 agent participates in the **test**
+> lane — `01-test.yml` is Jetson-only. Source of truth for the policy:
+> `_docs/02_document/tests/environment.md`.
+
 ## Decision Record (cycle-1 scope)
 
 | Decision | Choice | Rationale |