Non UTF8 clone errors are not stored

Created by: ryanslade

We've seen this on a customer instance:

t=2021-03-31T13:19:29+0000 lvl=eror msg="failed to clone repo" repo=REDACTED error="clone failed. Output: remote: Enumerating objects: 124, done.        \nremote: Counting objects: 100% (124/124), done.        \nremote: Compressing objects: 100% (96/96), done.        \nremote: fatal: unable to read REDACTED        \nremote: aborting due to possible repository corruption on the remote side.\nfatal: early EOF\nfatal: index-pack failed\n: exit status 128"
t=2021-03-31T13:19:29+0000 lvl=warn msg="Setting last error in DB" error="setting last error: ERROR: invalid byte sequence for encoding \"UTF8\": 0x00 (SQLSTATE 22021)"