Update individual Release page to use GraphQL
Problem to solve
The main Releases page (this one, for example) uses GraphQL (implemented in #214241 (closed)), but the individual Release page (this one, for example) still uses the REST API.
Proposal
Update the individual Release page to use GraphQL.
Further details
This will be much simpler than converting the main Releases page, because:
- We know we already have all the data we need in the GraphQL endpoint
- We don't have to deal with pagination, since this page only shows a single release
- This was the primary source of complexity when completing #214241 (closed).
- We already have patterns in place for making GraphQL queries for this data
Benefits
Currently, any improvements we make to the Releases page that involve backend data (for example, something like this) will only be visible on one of the pages (depending on which endpoint we update).
After this change, these pages will automatically stay in sync because they will both be using the same endpoint (GraphQL).
Permissions and Security
There should be no changes to permissions or security as part of this change.
Documentation
No documentation is necessary for this change.