Fix non-retrying bridges after retried builds in CI pipelines

What does this MR do?

Related to #213456 (closed)

When a job fails, subsequent jobs are skipped. After the failed job is retried, subsequent skipped jobs are marked as "processable" (created state).

However, subsequent bridge jobs are not marked as "processable", and this MR fixes that problem.

Example pipeline YAML files:

# .gitlab-ci.yml

build:
  stage: build
  script:
    - exit $((RANDOM % 2))

trigger_job:
  stage: deploy
  trigger:
    include: .child-pipeline.yml

# .child-pipeline.yml

deploy:
  stage: deploy
  script:
    - echo deploy

First run:

Second run:

What it needs to be:

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• 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