bw/bundles/crs-worker: don't deploy rsync-to-storage by default

Having both rsync-to-storage and rsync-from-encoder has lead to confusion
in the past about which is the correct unit to start, and what transfers
to where. By removing one of those units, we can avoid that situation
altogether.

bundlewrap/bundles/crs-worker/items.py

@@ -104,15 +104,19 @@
 }
 
 files['/usr/local/sbin/rsync-to-storage'] = {
-    'owner': 'voc',
-    'mode': '0700',
+    # only use this for REALLY weird network situations
+    'delete': True,
+    #'owner': 'voc',
+    #'mode': '0700',
 }
 
 files['/usr/local/lib/systemd/system/rsync-to-storage@.service'] = {
-    'content_type': 'mako',
-    'context': {
-        'slug': node.metadata.get('event/slug'),
-    },
+    # only use this for REALLY weird network situations
+    'delete': True,
+    #'content_type': 'mako',
+    #'context': {
+    #    'slug': node.metadata.get('event/slug'),
+    #},
     'triggers': {
         'action:systemd-reload',
     },