Cut a release that builds with a currently supported version of Electron

I'm the packager for the official Arch Linux packages for Keybase. They are **terribly** out of date because all current builds have been failing to build on any currently supported version of Electron for some time. At the time the current 6.2.x releases were made Electron26 was supported, but it went EOL shortly afterwards and we were never able to get it build. The package is currently stuck on 6.0.x, and even at that the relic of an Electron package it depends on is going to get dropped soon.

If we don't get a solution for building with *current* dependencies then it is going to get downgraded from official package status to an AUR package where end users have to build it themselves and work out the mess on their own.

Current supported versions are 28, 29, and 30. Please make a bump to something that is not EOL a priority so that downstream packaging can happen smoothly.

Looking around the issue tracker it looks like Fedora and others are having trouble because of this too and just using a current Electron build should make a *lot* of issues go away.

For a security focused app ecosystem it is unreasonable to expect people to run it on an EOL version of Electron & Chromium that is no longer being patched for known security issues.

No file, test, or entry point is named. Start by reproducing the current build with Electron 28, 29, or 30 and tracing the release and packaging configuration involved. Done means a release builds with a currently supported Electron version so downstream Arch and Fedora packaging can proceed.

Written by the indexing model from the issue text.