fix: ensure progressive releases show in release ui

[Lukewh]

Done

• Updated logic around showing progressive releases
• prettier went ham, sorry

How to QA

• Visit https://snapcraft-io-5119.demos.haus/snapd/releases and compare progressive release data with https://snapcraft.io/snapd/releases
  • The demo should display the data, the live site does not
• Visit https://snapcraft-io-5119.demos.haus/snapd/releases and compare progressive releases data with to snapcraft status snapd
  • The information in both should match

Testing

• This PR has tests
• No testing required (explain why): Legacy, none of this has tests :(

Issue / Card

Fixes #

Screenshots

[webteam-app]

Demo

Jenkins

demos.haus

[Copilot]

Pull Request Overview

This PR fixes the progressive release display logic in the release UI while cleaning up code formatting and export order.

• Updated the conditional logic for adding progressive channels.
• Simplified progressive release checks in the revisions list row.
• Reordered exports and adjusted formatting for consistency.

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
static/js/publisher/pages/Releases/releasesState.js	Changed progressive check from AND to OR to include releases with either percentage value defined.
static/js/publisher/pages/Releases/components/revisionsListRow.js	Added an extra condition for progressive releases and used a ternary that can be simplified.
static/js/publisher/pages/Releases/components/revisionsList.js	Reordered exports and added trailing commas for improved readability.
static/js/publisher/pages/Releases/Releases.tsx	Reordered imported components for consistency.
static/js/publisher/pages/Metrics/metrics/graphs/activeDevicesGraph/tooltips.ts	Adjusted the tooltip position logic with minor formatting changes.

Comments suppressed due to low confidence (1)

static/js/publisher/pages/Releases/components/revisionsListRow.js:45

• [nitpick] The ternary operator is redundant here; returning the boolean expression directly would simplify the code.

revision.prog_channels.includes(`${track}/${risk}`) && revision.progressive ? true : false;

[steverydz]

LGTM 👍