Parent Issue

Part of #1039

Problem

The `test-integration.yml` workflow is actually just a TypeScript type-check. It does not run the integration test suite. This means 20+ integration test files covering domains, DNS, environment variables, exit codes, error handling, network security, credentials, and protocols have no CI pipeline.

Only the 5 chroot test files run in CI (via `test-chroot.yml`).

Acceptance Criteria

• Create a new CI workflow (e.g., `test-integration-suite.yml`) that runs the non-chroot integration tests on PR and push to main
• The workflow should build containers locally (`--build-local`) like `test-chroot.yml` does
• Should require Docker and sudo access (ubuntu-latest runner)
• Should have appropriate timeout (30-45 minutes)
• Should run the tests serially (integration tests can't run in parallel due to shared Docker resources)
• Consider splitting into groups (domain/network, protocol/security, container/ops) for parallel CI jobs

References

• Look at `test-chroot.yml` for the pattern to follow
• Integration test files are in `tests/integration/`
• Exclude `chroot-*.test.ts` files (already run by `test-chroot.yml`)

Closes #1039 (when combined with other sub-issues)