What This Does

• Improve checking for rsync errors in initial sync
• Suggest to user what might be wrong (in this case, missing rsync in remote environment)

Background

While trying out coder-cli on my own dev server, I had used a base ubuntu docker image for my environment. It doesn't install rsync by default, socoder sync fails with obscure "rsync: exit status 12".

It took a while for me to realizersync wasn't installed in the environment. We should make coder-cli suggest actions to resolve the issue to the user.

Also, I suspect the existing check for incompatible rsync protocol won't work, as the errors returned from the sync internal package are xerrors vs. the plain error type declared to compare errors against. When I tried adding the equivalent check for error status 12, following the example for exit status 2, the comparison did not work.

I know it's cheezy to compare literal string representations of errors in Go -- so if a better method is suggested I'll use that instead.

Example 'improved' output if remote environment has no rsync installed

$ ./coder sync foo russ-env1:/home/coder/newpath2020-06-24 11:41:03 INFOdoing initial sync (/home/russtopia/dev/coder-cli/cmd/coder/foo -> /home/coder/newpath)2020-06-24 11:41:04 FATALerror in rsync protocol datastream (no installed remote rsync?)