Reduce amount of information relayed on error to the front-end

This will show up a generic short message to the front-end while still logging the full message via the logger service.
Ready for review.

Proposed message:

I think this is a great idea.

I would maybe rephrase the error, though. How about something like:

An error occurred while fetching data from drupal.org. See the error log → for details, or report the issue → . While this error persists, you can browse the project catalog on drupal.org → .

Suggestion from #7 about the text applied, except that I didn't offer a link in the words "error log" and that the link to report an issue is against the "drupalorg" project. We can triage the issue from there and move back to PB queue if needed (also, PB might be merged into core at some point so the link would need to change).

fjgarlin → credited tim.plunkett → .

One further suggestion but otherwise I'm fine with your changes.

Suggestion applied.

Not sure how to manually test this, but I think that this is a much better user experience which doesn't compromise debuggability, since it logs the original error.

Easy to test manually via Drupalpod. See the change that I cleaned up in this commit: https://git.drupalcode.org/project/project_browser/-/merge_requests/685/...

If you add that bit, you can see the error message. Just don't commit it (like I did 🙈).

Clean up error messages, always a better UX.

Some language nitpicks https://git.drupalcode.org/project/project_browser/-/merge_requests/687/...

Fine with that.

Automatically closed - issue fixed for 2 weeks with no activity.