CI: run the container mirror job after the VM job hydrated the mirror

[piob-io]

Summary

test-git-mirror-container now has needs: test-git-mirror.

The push run for #55 (run 35223527121) failed only in this job: the repository's mirror entity had been purged, test-git-mirror and test-git-mirror-container started together, the VM job got to hydrate the fresh entity and the container job was answered with Another job is hydrating the git mirror cache → direct clone → Sticky disk is not mounted inside the container; the mirror path was not exercised (the container job fails hard on push by design). The chain is now VM (hydrates/commits) → container → VM-after-container, which is also the ordering the takeover assertions describe.

Link to Devin session: https://app.devin.ai/sessions/a3b42ef15226438faf3f9cdde9662918
Open in Devin Desktop: https://app.devin.ai/desktop/session/a3b42ef15226438faf3f9cdde9662918?variant=devin
Requested by: @piob-io

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled. (Staging)}

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring