An access has an id, and its mounts name it (issue 153)

Ten definitions name each access by id; the path stays as the default an assignment may replace,
and the host side of every mount says ${access:<id>}. Resolved with no placement, every definition
names exactly the paths it named before (TestPlacedDirectoriesKeepTheirPaths, extended). On an
adopted machine the assignment now says `accesses: {<id>: <path>}` and the mount follows.

Needs the controller that knows an access id (mesh-controller #176); the running one refuses the
field at registration.

modules/bazarr/module.json

@@ -22,18 +22,22 @@
   ],
   "accesses": [
     {
+      "id": "movies",
       "path": "/services/media/movies",
       "mode": "read-write"
     },
     {
+      "id": "series",
       "path": "/services/media/series",
       "mode": "read-write"
     },
     {
+      "id": "anime",
       "path": "/services/media/anime",
       "mode": "read-write"
     },
     {
+      "id": "downloads",
       "path": "/services/media/downloads",
       "mode": "read"
     }
@@ -67,10 +71,10 @@
       ],
       "volumes": [
         "/services/bazarr/config:/config",
-        "/services/media/movies:/movies",
-        "/services/media/series:/series",
-        "/services/media/anime:/anime",
-        "/services/media/downloads:/downloads"
+        "${access:movies}:/movies",
+        "${access:series}:/series",
+        "${access:anime}:/anime",
+        "${access:downloads}:/downloads"
       ]
     },
     {