fix: remove demo, staging and review environments

Rather than maintaining the Kubernetes config for pubsweet-starter, we're looking at removing it from the cluster altogether The deployment requires around half a CPU core to be allocated for it, which is putting a strain on our resources.

Going forward, we can provide templates and skeletons for clients to use with pubsweet-starter if they want to investigate hosting options.