Pipeline promotion state is inconsistent between users viewing the same pipeline

## Summary
Two users viewing the same Next-Gen DevOps Center pipeline see different promotion state for the same work item.

One user can see the promotion in the **Production** stage, including the message:

> Promotion initiated, waiting for test execution to complete.

The other user does not see that promotion in Production at all. Instead, the work item remains shown as ready for custom promotion in **UAT**.

## Expected behavior
All users with access to the same DevOps Center project and pipeline should see the same current pipeline/promotion state for a given work item, subject only to intentional permission-based restrictions. A promotion already initiated toward Production should not be absent for another authorized user.

## Actual behavior
The visible state differs by user for the same pipeline and work item:

- **User A:** sees the active promotion under Production.
- **User B:** does not see that promotion and sees the item as still ready to promote from UAT.

## Impact
This creates uncertainty about whether a deployment was actually initiated and risks duplicate or conflicting promotion actions.

## Context
- Same DevOps Center pipeline: `CarvagoPipeline`
- Same work item / promotion flow
- Stages involved: UAT → Production
- The discrepancy was observed concurrently in separate user sessions.

Reproduce the discrepancy by opening CarvagoPipeline in two authorized user sessions and observing the same work item across UAT and Production. Compare the promotion state and permissions in each session; done means both users see the same current state for the UAT → Production promotion.

Written by the indexing model from the issue text.