ci(wip): make the release workflows more generic and remove dependency from jsonnet

[fcjack]

What this PR does / why we need it:

When trying to update our workflows me and @paul1r realized that the images and release workflows are generated using the jsonnet.

The current generated workflow is doing some duplication and playing with the quotes is hard to double check the generated file.

Trying to make one PR for the images workflow first that would make this more reusable.
We are defining a workflow that is responsible to build and push the images, this workflow will receive a set of inputs that will allow us to customize the workflow.

Advantages:

• No code repetition
• To add a new image we only need to add a new job call with the right parameters
• Workflow file consistency, we are following the syntax and standards of workflow definition

Special notes for your reviewer:

To avoid a way bigger PR decided to create one only for images and the release workflow will be in a different PR.
Updated the check.yml to validate the config since is a small workflow

Checklist

• Reviewed the CONTRIBUTING.md guide (required)
• Documentation added
• Tests updated
• Title matches the required conventional commits format, see here
  • Note that Promtail is considered to be feature complete, and future development for logs collection will be in Grafana Alloy. As such, feat PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.
• Changes that require user attention or interaction to upgrade are documented in docs/sources/setup/upgrade/_index.md
• If the change is deprecating or removing a configuration option, update the deprecated-config.yaml and deleted-config.yaml files respectively in the tools/deprecated-config-checker directory. Example PR