Tag docker build images so we can build older releases properly

In THRIFT-4506 we identified an issue in our build process.  Without creating long-term docker image tags in Docker Hub for our build images, we may find ourselves in the situation we were in for 0.9.3.1, which is inability to make a build environment due to retired and removed third-party software.

When releases are made, the docker image that was used in CI to build it (in the thrift/thrift-build hub) should be tagged with the version number of the release so we can come back to it if we need to in order to release a patch.

We shoud tag, as quickly as possible, what we're using today, so we have a 0.12.0 compatible build environment that works in the future.