Make troubleshoot feature discoverable outside of job logs page

Release notes

Problem to solve

In #473091 (closed) we made a change to the position of the troubleshoot button to be closer in proximity to the starting point of failure investigation. (This isn't being tracked, so we're unable to tell the impact this change has had on discoverabilit.)

There's no valid reason to keep this trigger limited to job logs page given users identify failed job much earlier(MR page, List view) and can get the same result from anywhere else.

Intended users

Software developers- Sasha

User experience goal

The workflow to troubleshoot a pipeline failure using RCA can be shorter.

Proposal

1. Place troubleshoot trigger in failed pipeline widget in MRs.
2. In Jobs tab in pipeline detail page:
   1. 

Further details

Permissions and Security

Documentation

Availability & Testing

Available Tier

Feature Usage Metrics

Number of clicks for each of the discovery point.

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

What is the competitive advantage or differentiation for this feature?

Links / references