[Metricbeat] gcp: update sample datas

[endorama]

What does this PR do?

This PR updates gcp module sample events.

Why is it important?

Sample events have not been updated as part of #27974. Integrations tests are broken due to this mismatch, as has been discovered working on elastic/integrations#2301

There are some notes to this:

1. we don't run GCP integrations tests in the CI, so we were not able to catch these
2. the method for updating this sample data (go test -data) is not well documented

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[mergify]

This pull request does not have a backport label. Could you fix it @endorama? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[endorama]

I'm facing some issues in updating the data: for compute module, the update code is not able to fetch events. For billing module it seems the -data flag is not available, so it cannot be run. Debug in progress

[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

• Reason: null

• Start Time: 2022-02-03T10:14:48.081+0000

• Duration: 94 min 23 sec

• Commit: fe18e23

Test stats 🧪

Test	Results
Failed	0
Passed	2763
Skipped	240
Total	3003

💚 Flaky test report

Tests succeeded.

🤖 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!)

[jlind23]

@endorama closing for now until further updates.