Add info about the releases button to release notes top bar

[soupslurpr]

resolves #47

Before

After

[soupslurpr]

Actually, maybe outlined is a better choice rather than filled since it isn't an important button? Chromium also seems to do this with their settings screen help button.

[soupslurpr]

I went ahead and pushed the outlined icon since I think it fits better and the inspiration for the button placement (Chromium settings help button) also uses an outlined icon. Feel free to respond with feedback if anyone thinks this isn't the right choice.

[thestinger]

It would probably be nicer to include the info inside the app.

[thestinger]

Would mean having to keep it in sync but we already have to do that for a lot of this (community and donate).

[soupslurpr]

It would probably be nicer to include the info inside the app.

Maybe in a dialog that opens when pressing the info button?

[matchboxbananasynergy]

While it would probably be nicer to include the information in-app, it would be another thing that has to be synced/maintained in the app, and the text would have to be adjusted to make sense in the context of the app, rather than the "Releases" page on the website.

As an example, the following phrase wouldn't make sense in-app:

GrapheneOS uses automatic over-the-air updates, but full update packages are listed below for uncommon use cases like never connecting the device to the internet.

Taking the people to the website to read about this also introduces them to where they can get the releases from in case they want to sideload, which is a potential bonus/benefit.

Additionally, we already use this UX for Vanadium (help icon on the top right in Vanadium settings takes you to the usage web browsing guide).

[matchboxbananasynergy]

I think that if we insist on including the information in-app, most of that section shouldn't be included. It would probably be enough to include the last paragraph only:

Releases are tested by the developers and are then pushed out via the Alpha channel. The release is then pushed out via the Beta channel shortly afterwards. Finally, the release is then pushed out via the Stable channel after being tested by some users using the Beta channel. In some cases, problems are caught during Beta channel testing and a new release is made via the Beta channel to replace the aborted one. In general, it's not possible to downgrade unless a downgrade update package is generated, so use the Stable channel if you cannot tolerate dealing with temporary issues while a new release for the Beta channel is being created.