One object store, not two

object-store.json and minio.json described the same thing: same image,
same provision at the same scope, same provisioner. Not two
implementations a person could choose between — one module written
twice. Assigning both to a node would have collided on `s3-bucket`.

It exists because it was written first, to pair with photos.json for the
README's worked edge, and minio.json was the fuller version of the same
module written later. Nobody removed the first.

The pair test keeps its point and now reads the surviving one. Checked
across the rest: this was the only duplicate.

examples/modules/modules_test.go

@@ -220,12 +220,17 @@ func TestTheResolverDoesNotAskItselfForUpstreams(t *testing.T) {
 
 // The two halves of an object-store edge, as a pair.
 //
+// `minio.json` is the provider. There were two manifests describing the same object store — the
+// other named `object-store.json` — which is not a choice between implementations but one module
+// written twice: same image, same provision, same scope. Assigning both to a node would have
+// collided on `s3-bucket`.
+//
 // A provider and a consumer that only ever appear separately are two manifests nobody has checked
 // against each other: the name one provides has to be the name the other requires, and the key a
 // consumer contributes has to be the one the provisioner reads. Both were got wrong while writing
 // them, and neither would have been caught by parsing either file alone.
 func TestTheObjectStoreEdgeFitsTogether(t *testing.T) {
-	provider := read(t, "object-store.json")
+	provider := read(t, "minio.json")
 	consumer := read(t, "photos.json")
 
 	const provision = "s3-bucket"