[Reporting] Improve "Max attempts reached" failure message

[tsullivan]

When a reporting job fails with "Max attempts reached". it indicates the screenshot couldn't be completed before the timeout of xpack.reporting.queue.timeout. However, there are separate timeouts in play, such as the timeout of waiting for the Kibana URL to open (xpack.reporting.capture.timeouts.openUrl)

We should make it more obvious that Max attempts reached means the page couldn't be captured in time before the queue timeout

Users may see a message that they should increase the "open URL timeout" when we detect that the Kibana URL is taking too long to open. It should be more obvious that this timeout is for a part of the screenshot capture sequence, and increasing that setting doesn't guarantee a report can finish in time before the queue timeout.

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[elasticmachine]

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

[tsullivan]

This was solved in #64853