Consider naming the binary artifacts so they are easier to download

It would be nice if I could automatically download the right artifact for my current system using something like:

```
curl -sSL https://github.com/bazelbuild/bazelisk/releases/download/v1.12.0/bazelisk-linux-$(uname -m)
```

But I cannot, because the artifact names do not match the output from `uname -m` (or `uname` with any other option). Maybe you can recommend a different way to automate this, or maybe consider renaming the artifacts so they match the output from the standard Linux tools?

Start by inspecting the artifact names published in the v1.12.0 release and comparing them with the output of Linux uname tools. Determine whether renaming artifacts or documenting an automation-friendly mapping is the intended direction; done means users can reliably select the artifact for their system.

Written by the indexing model from the issue text.