Fix reporting metrics not supported warning for BigQueryIO Direct read when throttled

[Abacn]

Fixes #30646. Actually the feature is there but there is a bug prevented it from working properly.

The pipeline, when throttled, can see warning

Reporting metrics are not supported in the current execution environment.

raised from here:

beam/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryServicesImpl.java

Line 1676 in 8454cc9

throttlingMsecs.inc(delay);

This is because the method is called on a callback thread that does not have thread level metrics container. Change it to increment the metrics back to StorageClientImpl temporarily then add it to Beam metrics in work item thread resolved the issue.

Tested with reading TPCDS_1T

Before (pipeline throttled, slowdown, scheduler aggressively upscale worker):

• max worker 106

After (pipeline actively scale down, throttling metrics shown)

• throttling-msecs 15,060,000
• max worker: 57

Sufficient quota:

• max worker: 43

Please add a meaningful description for your change here

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[github-actions]

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

[Abacn]

assign set of reviewers

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @m-trieu for label java.
R: @ahmedabu98 for label io.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[Abacn]

macos java unit test failed due to #31100 - and rerun doesn't work because the base branch of this PR wasn't updated

[ahmedabu98]

This looks great, thank you for this fix!