I forgot to do this when migrating from Flake8 to Ruff.

Fixes b09df9bd

flake8 was dropped in b09df9bd, and
this is a left-over that allows us to drop the setup.cfg file

Only 3.8 is not EOL, and it's just some months. Even Debian old stable
is currenly on 3.9

According to
https://wheel.readthedocs.io/en/stable/user_guide.html#building-wheels
universal = 1 is opt-in

See similar patch in pmbootstrap for rationale:
https://gitlab.com/postmarketOS/pmbootstrap/-/commit/27618d5ffdb0b6cbf9471dc01a2ed14e1655ced0

We use this in pmbootstrap, and it is currently necessary to use Ruff.
Issue about moving Ruff to community:
https://gitlab.alpinelinux.org/alpine/aports/-/issues/15693

So we don't need to repeat it.

Repurposing argcomplete as a boolean telling whether the module
argcomplete was found results in a variable with two distinct purposes
and types, which is bad practice and confuses Mypy. As such, don't
assign False to argcomplete if the module is not found and instead just
check for whether it exists in sys.modules to determine whether it was
imported successfully.

This works in practice, but Mypy does not understand it, and I'm not
sure how to best resolve it.

`mrhlpr status 123` on a non-checked-out branch would panic because
`commits_follow_format` was an undefined variable.

Right now you can't switch branch if there are any untracked files. This
is not something that git checkout has a problem with generally, so
don't consider the worktree unclean if the only "impurity" is untracked
files.

Fix the part that inserts an empty line after the first line, before
adding the label.

Add basic logic to detect when we should insert a trailer line at the
end of the commit message, before adding the CI label.

Add a new command-line argument to add the frequently used skip-build
label with the default text.

fixes #11

per the documentation in
https://setuptools.pypa.io/en/latest/userguide/datafiles.html
include_package_data requires also specifying what it is

Forgot to bump the version in mrhlpr/__init__.py, so let's tag a fixup
release.

Add riscv64 for... well you know it, and also arm64 -> aarch64 for
aarch64-darwin systems similar to this patch:
https://lists.sr.ht/~postmarketos/pmbootstrap-devel/%3C167000939722.18650.8735853729695007724-0@git.sr.ht%3E

Currently "riscv64" jobs are named "riscv64-emulated" in alpine (in pmOS
it's just "riscv64"). Adjust the script so it finds both.

Keep going if the pipeline status is not "success", just print a warning
instead of failing completely. Sometimes it makes sense to use this even
if the overall status is still "running", for example right now I
submitted a MR to alpine and the ppc64le build didn't start even though
the aarch64 build was complete already.

Always get the api call to the latest pipeline without cache, so we
don't miss newer pipelines. The comment already said so, but the code
still used the cache unless running with mrtest --no-cache.