Retry on connection reset

[RustyNova016]

Due to AI scrappers hammering MB, sometimes there's connection reset errors:

Would be great if request could be auto retried if it happens.

[kellnerd]

Unfortunately this king of error is exposed as a generic TypeError, so this probably requires parsing the error message in some place:

harmony.server [ERROR] TypeError: error sending request for url (https://musicbrainz.org/ws/2/url?inc=artist-rels%2Blabel-rels%2Brelease-rels&resource=https%3A%2F%2Fopen.spotify.com%2Fartist%2F7BagjRspbJJaxUzVFrYUBk): client error (Connect): Connection reset by peer (os error 104)
    at async mainFetch (ext:deno_fetch/26_fetch.js:192:12)
    at async fetch (ext:deno_fetch/26_fetch.js:475:11)
    at async MusicBrainzClient.#request (https://jsr.io/@kellnerd/musicbrainz/0.4.2/client.ts:261:18)
    at async MusicBrainzClient.get (https://jsr.io/@kellnerd/musicbrainz/0.4.2/client.ts:236:22)
    at async MusicBrainzClient.lookupByUrl (https://jsr.io/@kellnerd/musicbrainz/0.4.2/client.ts:191:58)
    at async lookupUrlToMbidMapping (file:///home/david/Code/MusicBrainz/harmony/musicbrainz/mbid_mapping.ts:150:18)

The above example shows that this can also happen during MBID mapping, where it is not as critical and doesn't necessarily have to be retried in order to serve page content.

Anyway, I think it would make more sense to have a retry option in my MB client rather than implementing it in all places where Harmony uses the client.

[RustyNova016]

Oh no. And I thought the way I had to fix it for Alistral was awful...

But yes, this is more of a client problem, not harmony. Feel free to move the issue around