Draft: Implement bridge retry to retry downstream pipeline

What does this MR do?

In this MR, we add a "retry" button to bridges in pipelines. It will be used for retrying the downstream pipeline if there is any failed job in it.

This draft implementation is just about asking the question that if this makes sense.

I thought maybe we are "abusing" the retry mechanism of jobs because we add the button in the bridge jobs.

Related to #32559 (closed)

The discussion: #32559 (comment 523152303)

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because _____.
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team