Stop bothering with version numbers #169
Description
At the moment, Try PS uses version numbers which sort of follow the compiler versioning; see https://github.com/purescript/trypurescript/releases. This is a little awkward, because sometimes we want to make more than one Try PS release for each compiler release. For instance, I'm about to tag and deploy a version which is based on v0.13.6 of the compiler, but I've already tagged one such version, so I'm going to have to call the new one v0.13.7 or something, even though no such PureScript release exists.
This has potential for confusion, and I don't think Try PS version numbers really mean very much anyway. I think we should stop bothering with version numbers for Try PS, and instead just keep track of the hash of the commit we deployed from, and preferably also the date of that commit. Right now, deployment is based on tags, and the tag names aren't required to conform to semver or anything, so we could start making tags like v2020-05-03.1 to avoid having to come up with meaningless version numbers. I'd also like to set the version in trypurescript.cabal to 1.0 and then leave it alone and not use it for anything.