Review Deployment Processes

[da2ce7]

GitHub no longer supports environments from tags. - This means we need to rework our deployment process using the new namespace convention: release/**/*.

It is possible to create the tag, after the deployment environment has executed; and in the ruleset enforce this.

It appears that the new semantics versioning release branches follow the following convention: e.g. refs/heads/releases/v1.2.3-beta.1

After making the deployment; then we can make a tag with the same version. However this will not trigger any workflow.

GitHub no-longer supporting tags as deployment environments is surprising; and somewhat of an unintuitive choice.