[registry-facade] Do retry if copying a blob fails mid way

[geropl]

Description

We do retries when doing HTTP requests. But if an error occurs while copying the response body, we did not re-establish the connection so far. This PR justs does this, as well as extending the backoff time span to ~10s instead of 1s, to be able to cover intermittent network problems.

Related Issue(s)

Fixes CLC-1416

How to test

• new tests are green: ✔️
• start a workspace ✔️
• start an image build: ✔️

Documentation

Preview status

gitpod:summary

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft preemptible
  Saves cost. Untick this only if you're really sure you need a non-preemtible machine.
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[corneliusludmann]

solid fix for the network retry issue, good test coverage

[geropl]

/unhold