Ensure atomic releases - binary and docker images are same

[spiceai]

Ensure atomic releases - binary and docker images are same

[phillipleblanc]

We'll solve this with a process change and a code change.

Process change

Whenever we "release" we will update version.txt to the version we would like to release to, i.e. 0.1.0-alpha.4. We push this change and the CI system will automatically upload a new release to that version tag. We will then immediately update the version.txt to the next highest version suffixed with -rc. I.e. after releasing 0.1.0-alpha.4 we would change version.txt to 0.1.0-alpha.5-rc. The install script will ignore versions that have rc in it, so this allows us to ensure the "released" version is the one being picked up by users, while allowing us to iterate on the next rc version. When we want to release the rc version, we change version.txt to remove the rc, release it, change version.txt to the next highest version with rc and repeat.

Code change

There are two code changes needed to support this: the CLI should only try to run the same version of the runtime as the CLI version itself. This is being worked on in #80. The next change is that the rc builds should be overwritten on each check-in to trunk. Currently the docker build is overwriting on every check-in, but the CLI and spiced binaries only get uploaded once and every subsequent time the CI tries to release them it silently fails.