Localization update feature logs 404 errors too aggressively

I don't understand why this is postponed based on my comment in #31. In that comment I think I outlined the work that needs to be done here next. I am setting back to needs works.

I like where this is going. But why are we so worried about removing these noisy log messages? I've got a 40+ language website that we have a full install profile test suite setup. For me, the issue is deeper. Because we do a foreach on each module in each language, testing and installing the site from configuration takes a _really_ long time. In addition to logging to drush or watchdog, it would be nice to use async guzzle and call each of the URLs in a shorter time frame. It would speed up downloads. I think we'd need to concern ourselves with some type of poor mans throttle so we don't send off 1000 URL requests, or even 100. That higher volume of traffic might cause performance issues on the localization servers.

Sadly this needs another reroll for Drupal 10.2. Doesn't apply anymore.

Created MR for 11.x

#31 mentions an issue summary update which is still needed.

Also test coverage.

I would propose a slightly different approach, by marking the file with locale_translation_update_file_history() instead of locale_translation_status_save()

The patch attached