Refactor container workflows

[jcortejoso]

Description

Refactor the container workflows for building the sha and tagged (release) images. More importante changes:

• Using regctl as more flexible tooling for adding the tags
• add-docker-tag workflow now expects the full image references (registry/name:tag). This make it more flexible, although we'll need to run more jobs for doing the same
• Build geth-all image also tagged with commit sha.

Done as part as I was debugging issues in the workflow.

[github-actions[bot]]

Coverage from tests in ./e2e_test/... for ./consensus/istanbul/... at commit 8c10ff25ee0c13e7aea0a722ef2e6aff8987f73a

coverage: 51.1% of statements across all listed packages

coverage:  63.2% of statements in consensus/istanbul
coverage:  43.2% of statements in consensus/istanbul/announce
coverage:  56.0% of statements in consensus/istanbul/backend
coverage:   0.0% of statements in consensus/istanbul/backend/backendtest
coverage:  24.3% of statements in consensus/istanbul/backend/internal/replica
coverage:  65.6% of statements in consensus/istanbul/core
coverage:  50.0% of statements in consensus/istanbul/db
coverage:   0.0% of statements in consensus/istanbul/proxy
coverage:  64.2% of statements in consensus/istanbul/uptime
coverage:  51.8% of statements in consensus/istanbul/validator
coverage:  79.2% of statements in consensus/istanbul/validator/random

[github-actions[bot]]

[github-advanced-security[bot]]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.