ci: Container Tests 'Layer D — E2E' fails every commit — perry-container-e2e package renamed to perry-container-compose

[proggeramlug]

Summary

The Container Tests workflow's Layer D — E2E (Linux / docker) job fails on every commit because it invokes a cargo package that no longer exists:

cargo test -p perry-container-e2e --test e2e_container -- e2e_redis_smoke --test-threads=1
error: package ID specification `perry-container-e2e` did not match any packages
##[error]Process completed with exit code 101.

The workspace crate is now perry-container-compose (per Cargo.toml [workspace.members]); perry-container-e2e was renamed/removed but the workflow step wasn't updated.

Impact

Cosmetic but persistent: every commit (and every release tag) shows a red Container Tests check. It does not gate publishing (release-packages await-tests keys only on test.yml + simctl-tests.yml), so it's noise rather than a blocker — but it trains people to ignore red Xs.

Fix

Point the Layer D — E2E step at the renamed crate / correct test target (perry-container-compose), or remove the dead e2e_container invocation if that suite was intentionally dropped.

Context: noticed during the release-pipeline repair (v0.5.1116–1122).

[andrewtdiz]

I am taking this focused CI hygiene fix.

Planned scope: update the Container Tests Layer D E2E workflow so it invokes the current workspace crate/test target instead of the removed perry-container-e2e package. I will verify the workspace package/test names locally before editing and keep this separate from release/binary-size work.

[andrewtdiz]

Claimed and fixed in draft PR: #4459

Root cause: crates/perry-container-e2e and its e2e_container test target still exist, but the crate was no longer listed in root [workspace].members. The Layer D workflow command was therefore failing at Cargo package resolution before the env-gated E2E tests could run.

Fix: restored crates/perry-container-e2e as a workspace member and recorded the package in Cargo.lock, while leaving default-members unchanged.

Validation:

• reproduced the pre-fix failure: package ID specification \perry-container-e2e` did not match any packages`
• cargo test -p perry-container-e2e --test e2e_container -- e2e_redis_smoke --test-threads=1
• cargo test -p perry-container-e2e --test e2e_container -- e2e_forgejo_stack --test-threads=1
• cargo metadata --no-deps --format-version 1 confirms the package manifest is visible
• git diff --check
• ./scripts/check_file_size.sh

[proggeramlug]

Fixed by #4459 (restored perry-container-e2e as a workspace member so the Layer D E2E cargo invocation resolves again). Closing.