Add s3warm to Tools

[petfold]

Adds s3warm — an Amazon S3-compatible API gateway for Swarm — to the Tools section.

s3warm speaks the S3 REST dialect (SigV4 auth incl. presigned URLs and streaming signatures, multipart, versioning, tagging, SSE-S3, CORS) and translates it onto a Bee node, so the AWS CLI, boto3, rclone and existing S3 applications work against Swarm with only an endpoint change. It also surfaces Swarm-native capabilities S3 doesn't have: buckets as browsable bzz:// manifests with atomic snapshot/rollback, and private buckets with ACT-backed grants readable off-gateway from any Bee node.

• License: BSD-3-Clause
• 307 tests of Ceph's s3-tests conformance suite green in CI (executable claim)
• Prebuilt binaries for 5 platforms; verified against Bee 2.8.1 on a live node

One item, per the contribution guidelines; description is 126 characters, sentence case.

🤖 Generated with Claude Code

[crtahlin]

Approving — everything checkable in the description holds up.

• Description is 126 characters, sentence case, correct format; not already in README.md or archived.md.
• Repository is public, not archived, not a fork, BSD-3-Clause, with real source, tests, docs, goreleaser config and four releases carrying six binaries each.
• The claims verify: test/s3tests/passing.txt has 310 lines of which 3 are comments or blank, leaving exactly the 307 tests stated, and the conformance suite runs as its own s3tests.yml workflow rather than a one-off — all three workflows green.
• Tools is the right section: this is a gateway you run, alongside etherchunk and IPFS to Swarm, not a library you import. Swarm is intrinsic to it rather than a backend it can be pointed at.
• Merges onto main with no conflicts; awesome-lint clean, with only the two spelling warnings that already exist on master.

One thing worth naming rather than blocking on: the repository was created yesterday, so there is no maintenance track record to judge against the "genuinely maintained" bar in AGENTS.md. Everything else about it argues the opposite of a placeholder, so I am comfortable — flagging it only so the choice is explicit.

Worth noting this is the first entry to arrive as a clean two-line diff since the repository was normalised to LF in #43; previous additions needed a rebase.

Description generated with help of AI.