Investigate how to simplify the deployment workflows #2801

Description

The deployment workflows contain a lot of steps which we should be able to refactor into something more manageable.

Problems:

• Deployments rely on the docker build command while ideally a image simply pulled and deployed. Though for the deployment image to volume map in sensitive data we would need to set up a private registry if we want to continue using this method.
• Duplicate work
  • The deployment install dist step runs a lot of duplicate tasks the deployment build artifacts shouldn't be published publicly, but depends on all other install dist tasks.
• The job doesn't follow our best practices , see uses: https://github.com/search?q=org%3Aopenremote+toJSON%28secrets%29&type=code

Acceptance criteria

• Deployments can still be based on the GitHub event model i.e. on: push, pull_request, release, and workflow_dispatch events continue to deploy with the right settings and to the right target.
• The deployment job no longer contains build steps.
• Sensitive data like certificates and other secrets are manually configurable on the deployment target, with no or minimal involvement of GitHub
• The secrets used are safely loaded without serializing them in any way