Make robot interface thin

[shardros]

Weak coupling between usercode and the robot code is desirable as it reduces the security risk on thre brain and makes the understanding of the state of the brain more sensible. The Robot doesn't blow up when the usercode exits.

AS A person running robocon
I WANT a thin interface for the usercode to the robot libarry and the actual code avaiable over a network socket
SO THAT
DONE IS

1. Shepherd exposes the public methods of the robot object over a network socket
2. There is no tight coupling between shepherd and the robot object
3. Performance of R.see() is evaluated to ensure that it returning large matracies does not take significantly more time
4. If R.see() performance is anything more than 250ms worse an investigation into how to reduce the return payload is implemented.

NOTES:

• This is something which could get very complicated and it would be good to keep this as simple as possible.
• https://rpyc.readthedocs.io/en/latest/ this is an easy ready made solution
• The R.see() investigation must test:
  • all resolutions
  • images with and without april tags

Alternatives prebuilt RPC is:

• https://docs.python.org/3/library/xmlrpc.html
• https://zeromq.org/

@shardros 's Personal opion is taht RPPy should be used.