Include all Dockerfiles that use Golang into the bump job

[rdner]

What does this PR do?

So, we can avoid vulnerability reports from Snyk for the outdated images.

Why is it important?

Quite a few issues reported by Snyk have to do with the Docker images that we have for testing and development, so we should include them into updates to avoid extra reports from Snyk.

It's a follow up to #35919

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-06-27T15:57:01.669+0000

• Duration: 13 min 18 sec

Test stats 🧪

Test	Results
Failed	0
Passed	3
Skipped	0
Total	3

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[pierrehilbert]

LGTM

[v1v]

As a consequence of this change the updateCLI pipeline is not working:

update-version.asciidoc
-----------------------
✔ - all contents from 'file' and 'files' combined already up to date

ERROR: something went wrong in target "update-dockerfiles" : "no line matched in file \"./metricbeat/module/vsphere/_meta/Dockerfile\" for pattern \"FROM golang:\\\\d+.\\\\d+.\\\\d+\""

Pipeline "Bump golang-version to latest version" failed
Skipping due to:
	targets stage:	"something went wrong during target execution"

See this