audit-logger: the container names its image directly (a container has no artifact)

A container resource takes a digest-pinned image, not a build artifact — the
host refuses 'artifact' on a container. Verified: the mesh assigns it and the
host runs it in the lab.

modules/audit-logger/module.json

@@ -5,15 +5,6 @@
   "own-secrets": {
     "broker": "/var/lib/audit-logger/broker"
   },
-  "build": {
-    "artifacts": [
-      {
-        "name": "runtime",
-        "kind": "upstream",
-        "from": "registry.invalid/mesh-runtime-audit@sha256:0000000000000000000000000000000000000000000000000000000000000000"
-      }
-    ]
-  },
   "resources": [
     {
       "id": "state",
@@ -31,7 +22,7 @@
       "id": "run",
       "type": "container",
       "name": "mesh-audit-logger",
-      "artifact": "runtime",
+      "image": "mesh-runtime-audit@sha256:0000000000000000000000000000000000000000000000000000000000000000",
       "network": "host",
       "volumes": [
         "/var/lib/audit-logger/broker:/run/secrets/broker:ro",