Vendor grpc

[damccorm]

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.

[Abacn]

Thanks, can we merge it first?

Technically released artifacts should come from reviewed codes. In the past the vendor release was done in three step merge vendor PR -> build vendored jar on master -> update Beam to use vendored jar. I understand this PR is used to generate https://repository.apache.org/content/repositories/orgapachebeam-1396/ however by the time of vote this comment hasn't been merged

[damccorm]

Sure, we can merge this - thanks. I think that wasn't clear to me from the docs (maybe I misread), I'll do a pass to see if they need updated after the release