Added metadata-crawler dockerfile. Refactor container workflows

[jcortejoso]

Description

Blockscout metadata crawler is still an in-use tool to fetch celo explorer metadata from validators and validator groups.
The dockerfile for this was deleted (by error) in #10124.

This PR aims to restore the dockerfile, with optimizations/refactoring to reduce the number of packages and dependencies included and also having an updated image with reduced present vulnerabilities.

Apart from that, I've unified different container-* workflows in a single containers.yaml workflow, trying to improve readability and maintainability.

Tested

Tested in baklava. It executed correctly (although there were not any metadata change, but I expect to work normally).

Backwards compatibility

No backwards compatibility issue detected

[changeset-bot]

⚠️ No Changeset found

Latest commit: d08f583

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[aaronmgdr]

hmmi was thinking the meta data crawler was close to deprecated and had included it in the packages moved #10829 to the new repo for sdks. (with the thought that it would be removed in the next few months)

Do you want it to remain in the monorepo? where you could then move it to it own repo if its being kept around.

[jcortejoso]

hmmi was thinking the meta data crawler was close to deprecated and had included it in the packages moved to the new repo for sdks. (with the thought that it would be remove in the next few months)

Do you want it to remain in the monorepo? where you could then move it to it own repo if its being kept around.

Talked with Valentin and seem we still need it. It is probably only on maintainability mode and we won't be working on new features, so I'd expect very little job on its code (if any).

We can move to its own repo it that will make easier monorepo work.

[github-advanced-security]

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.