Missing default User-Agent from Http fetcher

GuzzleHttp decided to deprecate the getConfig() and it looks there is no easy replacement for it: https://github.com/guzzle/guzzle/issues/3114
That means I either have to remove this feature, find another way to implement it or ignore the deprecation warning for now. Ignoring it could mean that at some point in the future this feature might stop working.

Since no test coverage for this was added, it will be harder to try to find a replacement for this. Also because in #16 I said I wasn't able to reproduce the bug.

@dmundra, @andypost
Can you help with this?

MR 182 is merged manually.

Since this issue is now no longer fixed, I reopen it.

@dmundra said the following about this issue in Slack:

Thanks for working on this. I haven’t revisited that issue and I haven’t run into a case where I have used that module against a service that blocks empty user agents so I am not the best person to look into it right now. I will see if can follow up on the discussions in slack and in the thread but it going to be a while.

Reverting the changes make sense

See also https://drupal.slack.com/archives/C033S2JUMLJ/p1720346469627799

MegaChriz → closed merge request !182

So I think this is no longer an issue and so no fix is needed. I tested with a new Drupal site and the latests feeds branch and the requests working to even the site I had an issue with. So I think this should be closed.