test(cloud): remove redundant composite suite wrappers

Six cloud-shared composite lane files import24already-discovered test files and add only expect(typeof test).toBe("function"). Their comments claim independent isolation or complete lifecycle coverage, but they do not connect the imported suites into one lifecycle. The normal package runner recursively discovers every original test and owns process isolation.

A real Bun1.3.14 --isolate run confirms duplicate registration: shared billing original alone runs7tests/51assertions; original plus eliza-sandbox-16639-lane2-billing wrapper runs15tests/103assertions, with the same7behavioral cases twice plus1runner self-check. Tracked-reference search found no direct wrapper callers in scripts, manifests or workflows.

Scope: retire eliza-sandbox-16639-lanes2/3/4/5,provisioning-jobs-16639-lane and docker-sandbox-provider-lane (100lines total), retaining all24original suites and existing Windows quarantine/process sharding. Verify each original executes, compare retained test names, and investigate isolation requirements before removal. Do not replace real errors with skipped tests or claim independent unit suites constitute a complete lifecycle.

Acceptance: no unique behavior lost,no dangling consumers,no weaker runner isolation; package checks and root verification pass. The originals are currently being exercised in separate Bun processes; results are not yet complete.