[REQUEST] Clarify status chips for manually promoted release-track members

Is your feature request related to a problem? Please describe.
When auto-promote candidates is disabled for a standard release track, objects can be manually moved from Candidates to Staged. The object’s status chip (for example, “Work in Progress” or “Reviewed”) can conflict with or be confused for its release-track column, making its place in the release workflow unclear.

Describe the solution you'd like
Clarify the distinction between an object’s workflow status and its release-track state. Consider clearer labels, separate visual treatments, or contextual help so users can immediately tell both the object’s status and whether it is a Candidate or Staged member.

Describe alternatives you've considered
Users can infer the object’s release position from its column and its workflow status from the chip, but this is ambiguous when the labels convey different stages of readiness.

Additional context
This applies to standard release tracks with auto-promote candidates disabled, where manually staged objects may still have a “Work in Progress” or “Reviewed” status.

Reproduce the standard release-track scenario with auto-promote candidates disabled, then inspect how manually staged objects display their workflow status chip alongside the Candidate or Staged column. Compare the available label, visual-treatment, and contextual-help approaches; done means users can distinguish workflow status from release-track state immediately.