Move the artifact store's tools into a module beside it, as the controller requires

A module that provides the artifact store cannot build an artifact: building publishes to the store,
so the store would be needed to create itself, and the module check refuses it. The tools become
artifact-store-tools, assigned beside the store, and read manifests from the store's files through its
container as they already read the listing, so they need no address for the store's door. Named for
the artifact store, because "store" alone is the database server (hq glossary).

modules/distribution/module.json

@@ -16,16 +16,6 @@
   "capabilities": [
     "container-runtime"
   ],
-  "invokes": [
-    "seat:mesh-controller.artifacts",
-    "seat:mesh-controller.collect"
-  ],
-  "tools": [
-    "store_repositories",
-    "store_usage",
-    "store_references",
-    "store_collect"
-  ],
   "own-secrets": {
     "broker": "/var/lib/mesh/registry/broker"
   },
@@ -100,24 +90,5 @@
         "store"
       ]
     }
-  ],
-  "build": {
-    "artifacts": [
-      {
-        "name": "tools-go",
-        "kind": "bundle",
-        "language": "go",
-        "system": "arch",
-        "from": "cmd/store-tools",
-        "binary": "store-tools",
-        "loads": [
-          "store-tools"
-        ],
-        "env": {
-          "MESH_STORE_URL": "http://127.0.0.1:${port:5000}",
-          "MESH_STORE_CONTAINER": "mesh-registry"
-        }
-      }
-    ]
-  }
+  ]
 }