Feature Request: Use standard naming convention for release packages by separating OS and ARCH

Description of the problem or steps to reproduce

Please consider adjusting the release names to separate the {os} and {arch} to assist automating the download of Micro from GitHub.

The lack of standard naming conventions makes it harder to automate the downloading of Micro from the GitHub releases. Almost all projects on GitHub separate the {os} from the {arch} in the release name. This allows for selecting one package based on the OS and ARCH of the current system. Micro doesn't follow these naming conventions making it harder to select a single package.

Considering only Linux, $GOOS and $GOARCH represent linux and [arm, arm64, 386 and amd64] respectively. Mapping this to the releases is non-trivial:

• micro-2.0.13-linux-arm.tar.gz
• micro-2.0.13-linux-arm64.tar.gz
• micro-2.0.13-linux32.tar.gz
• micro-2.0.13-linux64-static.tar.gz
• micro-2.0.13-linux64.tar.gz

Specifications

Version: 2.0.13
Commit hash: 68d88b57
OS: openSUSE Leap 15.4
Terminal: Alacritty

Start by locating the release packaging entry point that produces the listed Micro archives and reviewing how Go’s GOOS and GOARCH values map to their current names. Done means the release names separate OS and architecture consistently so a Linux package can be selected unambiguously from those values.