[BEAM-14519] Add website page for Go dependencies

[damccorm]

Right now Java and Python have dependency pages, but Go does not. This closes that gap.

✨ RENDERED ✨

---

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

• Choose reviewer(s) and mention them in a comment (R: @username).
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• 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.

[asf-ci]

Can one of the admins verify this patch?

[asf-ci]

Can one of the admins verify this patch?

[asf-ci]

Can one of the admins verify this patch?

[damccorm]

R: @lostluck

[lostluck]

I also like the idea of linking to:

https://deps.dev/go/github.com%2Fapache%2Fbeam%2Fsdks%2Fv2/

Which will list all versions of the module, and include the various scorecards and things automatically, and then the dependencies are also visible right there.

[damccorm]

I also like the idea of linking to:

https://deps.dev/go/github.com%2Fapache%2Fbeam%2Fsdks%2Fv2/

Which will list all versions of the module, and include the various scorecards and things automatically, and then the dependencies are also visible right there.

Unless we plan on staying on top of those warnings, I'm not sure I want to direct users that way. Security conscious customers will mostly already have a way of assessing their dependencies (or will find one), but most others will probably navigate to that page, be alarmed, and not have the context to tell if any of these dependencies actually matter to Beam.

If we're planning on getting green on that page and staying green then I care less (but I don't really see that being a high priority)

[lostluck]

Fair points. I may go ahead and try to clear them, but there's no need to highlight them.

[lostluck]

LGTM