core/remote: Catch un-replaced Chromium net errors
core/remote: Catch un-replaced Chromium net errors

  Some requests made via Electron's and thus Chromium's net stack can
  fail with obscure errors thrown in a way that makes them uncatchable.

  When these are thrown by Electron, their message contains `mojo result
  is not ok` and we already have some logic to handle them.
  However, it seems that some errors can come directly from Chromium
  without being replaced by the Electron's error and have the
  `ERR_HTTP2_PROTOCOL_ERROR` code.

  We were not handling these properly.

cozy-labs/cozy-desktop,cozy-labs/cozy-desktop,cozy-labs/cozy-desktop,cozy-labs/cozy-desktop