release: supersede the version that was published with files that are not the package (#3)

The previous version was tagged, released and mirrored, and then found to carry
two files that describe a machine rather than the package. Removing them changes
what the package is, and a published artifact cannot be changed: the mirror
allows neither replacing an asset nor deleting a release, which is the property
that makes a pinned sha256 mean something.

So the cleaned tree is a new version rather than a second meaning for the old
one. The old tag stands, is consistent in both regions, and is not carried by the
index; this is the version the index carries.

That is what a patch version is for, and the sequence is the reason the index is
the last gate rather than a parallel one: nothing had been written there yet, so
nothing has to be withdrawn.

Author: Sunrisepeak

README.md

@@ -5,10 +5,10 @@ written on the kernel's own calls.
 
 ```toml
 [dependencies]
-openkal = "0.5.0"
+openkal = "0.5.1"
 
 [target.'cfg(os = "macos")'.dependencies]
-openkal-macos = "0.3.0"
+openkal-macos = "0.3.1"
 ```
 
 Its purpose is as much to test the specification as to be used. A specification

mcpp.toml

@@ -1,14 +1,14 @@
 [package]
 namespace   = "mcpplibs"
 name        = "openkal-macos"
-version     = "0.3.0"
+version     = "0.3.1"
 description = "An implementation of openkal for macOS, written on the kernel's own calls. Its purpose is as much to test the specification as to be used."
 license     = "Apache-2.0"
 authors     = ["mcpplibs"]
 repo        = "https://github.com/mcpplibs/openkal-macos"
 
 [dependencies]
-openkal = "0.5.0"
+openkal = "0.5.1"
 
 [build]
 # The flags are attached to this package's own sources rather than to the whole