Step 2/3: Update individual Release page to use GraphQL

What does this MR do?

Updates the individual Release page (-/releases/<tag name>) to fetch its data from GraphQL instead of the REST API as described in #262667 (closed).

Context

The main Releases page (-/releases) was converted to use GraphQL in #214241 (closed).

Feature flag

This MR introduces a new feature flag, graphql_individual_release_page, which is disabled by default.

Screenshots

There should be no visible difference because of this change 🙂

Before/feature flag disabled	After/feature flag enabled

The Big Picture^TM

• Step 1 (!44766 (merged)): Add a new GraphQL query to fetch a single release
• Step 2 (this MR): Convert the page to use GraphQL
• Step 3 (!45170 (merged)): Enable the feature flag by default

Related to #262667 (closed)