Log gets spammed with "failed to read response body: context deadline exceeded "

This issue is somewhat related to #957. After I used `v1.1.5-0.20230123194941-3f5a6e9d6893` for quite a while I recently updated to v1.1.7 and noticed my log getting spammed by this output:

```
E1215 20:43:11.372250 45768 fetcher.go:292] https://sabre.ct.comodo.com: GetRawEntries() failed: failed to read response body: context deadline exceeded (Client.Timeout or context cancellation while reading body)
E1215 20:43:13.254103 45768 fetcher.go:292] https://mammoth2024h1.ct.sectigo.com: GetRawEntries() failed: failed to read response body: context deadline exceeded (Client.Timeout or context cancellation while reading body)
E1215 20:43:15.998639 45768 fetcher.go:292] https://sabre2024h1.ct.sectigo.com: GetRawEntries() failed: failed to read response body: context deadline exceeded (Client.Timeout or context cancellation while reading body)
E1215 20:43:16.379295 45768 fetcher.go:292] https://sabre.ct.comodo.com: GetRawEntries() failed: failed to read response body: context deadline exceeded (Client.Timeout or context cancellation while reading body)
```

I am using certificate-transparency-go as a library in my project. So I have two questions:

1. When exactly does this error happen? Is the CT log provider at fault? Is the log offline?
2. Is there a way for me to catch this error or to mute it?

Best regards,
Rico