fix(ci): preserve pipeline jobs after retries

Problem

glab ci view treated the first repeated job as the start of a retry-only suffix, so it dropped any distinct jobs later in the list, including downstream pipeline triggers appended after the jobs.

Change

Keep each job in its first display position and replace its displayed attempt when a retry appears. Use the stage and job name as separate key fields.

Validation

go test ./internal/commands/ci/view passed. The regression test covers a downstream entry after a retry.

Merge request reports

Loading
Loading