feat: Include build-error logs which are related to upstream for modules

[fiftydinar]

For akmods module, error is: "Could not depsolve transaction"
This error happens in these cases:

• when most-recent base image is failing to build
  (which causes non-matching version of akmods & Fedora kernel)
• when only most-recent akmods image is failing to build
  (this happened before, but it should happen rarely now due to setting higher priority for akmods repo)

Inform the user about this error case in build-time, with additional information:

• which upstream is responsible for this error
• link for the upstream repo for reporting issues
• that error should be reported only if issue is there for pro-longed time & if it's not reported already, to not cause issue-bloating to the upstream
• that they just need to wait for the issue to be resolved for builds to succeed

I think that rpm-ostree module can benefit from this too.

[xynydev]

Yeah, better error handling would be great. Less people asking about the same errors again and again.

[fiftydinar]

Should we close this one since docs on website contain the needed information?

This can potentially mitigate this issue too
blue-build/cli#171

[xynydev]

We can always also improve error logs IMO, better more info than less. Should probably link the docs on the website, though, instead of duplicating information.