Configure the remote timestamp channel to match reality

time aos_dump /roborio/aos/remote_timestamps/pi3 --count 1000 takes 5
seconds to exit.  This says we are sending at 200 hz.  The logger
got behind once on this channel, so let's up the rate to match reality.

Change-Id: Idc8639a014b629f600d032a8a7532109d41f7844
diff --git a/y2020/y2020_roborio.json b/y2020/y2020_roborio.json
index ec559d5..2e29eee 100644
--- a/y2020/y2020_roborio.json
+++ b/y2020/y2020_roborio.json
@@ -59,24 +59,28 @@
     {
       "name": "/roborio/aos/remote_timestamps/pi1",
       "type": "aos.message_bridge.RemoteMessage",
+      "frequency": 200,
       "logger": "NOT_LOGGED",
       "source_node": "roborio"
     },
     {
       "name": "/roborio/aos/remote_timestamps/pi2",
       "type": "aos.message_bridge.RemoteMessage",
+      "frequency": 200,
       "logger": "NOT_LOGGED",
       "source_node": "roborio"
     },
     {
       "name": "/roborio/aos/remote_timestamps/pi3",
       "type": "aos.message_bridge.RemoteMessage",
+      "frequency": 200,
       "logger": "NOT_LOGGED",
       "source_node": "roborio"
     },
     {
       "name": "/roborio/aos/remote_timestamps/pi4",
       "type": "aos.message_bridge.RemoteMessage",
+      "frequency": 200,
       "logger": "NOT_LOGGED",
       "source_node": "roborio"
     },