Link failure issue in e2e reliability report

What does this MR do and why?

In gitlab-org/ruby/gems/gitlab_quality-test_tooling!102 (merged), we copied failure_issue urls to test-metrics-*.json file which is used to push data to InfluxDB.

In this MR:

• We use failure_issue url in the reliability report as links on exception messages when failure_issue is available. Otherwise, continue to use the job_url as before.
• Extract exceptions_and_issue_or_job_urls into a method and add unit tests
• Remove limit from max_formatted_output_length to show full/non-trimmed output from RSpec failures.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Change the PROJECT_ID to an id of a project on your local.

From the qa/ directory, run:

GITLAB_ACCESS_TOKEN=<YOUR_PAT> CI_API_V4_URL=http://gdk.test:3000/api/v4/ QA_INFLUXDB_URL=https://influxdb.quality.gitlab.net QA_INFLUXDB_TOKEN=<QA_INFLUXDB_TOKEN_FROM_1P> bundle exec rake "reliable_spec_report[14, true]"

The above command is intentionally missing SLACK_WEBHOOK variable as we do not want to post to Slack for testing. This will cause an error but the issue will be created.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.