test: run the remote state tests against Garage instead of MinIO - #151

TL;DR

MinIO no longer publishes its image, so the integration stack can't start its S3 store. This swaps it for Garage, an open-source S3-compatible store, and the remote state tests run unchanged against it.

What & why

The remote state tests check that ctl saves and loads its state in an S3 bucket. They used MinIO as a local S3. Now that the image has gone, every integration run fails to bring up its stack. Garage works as a drop-in replacement for what these tests need. Its one difference is that the bucket and access key are created through its admin API rather than with mc.

Changes

• The compose stack runs a single-node Garage plus a one-shot setup container. The setup assigns the node, applies the layout, imports a fixed test key and creates the conduktor-state bucket.
• The remote state tests point at Garage's S3 port and key. Their helpers and test names now say S3 rather than MinIO.

Notes

• Locally I brought up only the Garage services from this compose file. ctl's own remote backend then loaded a missing state as empty, saved a state and read it back. The full integration run is left to CI because its ports clash with a stack I have running.
• docs/state_management.md still uses MinIO as an example, including a "MinIO for testing" recipe that pulls the old image. Those docs can move to Garage in a follow-up.

🤖 Generated with Claude Code

https://claude.ai/code/session_01B464sFQc8q6VkehfkByBaX