build(deps): bump the examples-golang-network group across 1 directory with 2 updates

[dependabot]

Bumps the examples-golang-network group with 1 update in the /golang-network/simple directory: github.com/envoyproxy/envoy.

Updates github.com/envoyproxy/envoy from 1.31.2 to 1.32.0

Release notes

Sourced from github.com/envoyproxy/envoy's releases.

v1.32.0

repo: Release v1.32.0 (#36597)

Summary of changes:

• Envoy now logs warnings when internal_address_config is not set.  If you see this logged warning and wish to retain trusted status for internal addresses you must explicitly configure internal_address_config (which will turn off the warning) before the next Envoy release.
• Removed support for (long deprecated) opentracing. 
• Added a configuration setting for the maximum size of response headers in responses.
• Added support for connection_pool_per_downstream_connection flag in tcp connection pool.
• For the strict DNS and logical DNS cluster types, the dns_jitter field allows spreading out DNS refresh requests
• Added dynamic metadata matcher support dynamic metadata input and dynamic metadata input matcher.
• The xff original IP detection method now supports using a list of trusted CIDRs when parsing x-forwarded-for.
• QUIC server and client support certificate compression, which can in some cases reduce the number of round trips required to setup a connection.
• Added the ability to monitor CPU utilization in Linux based systems via cpu utilization monitor in overload manager.
• Added new access log command operators (%START_TIME_LOCAL% and %EMIT_TIME_LOCAL%) formatters (%UPSTREAM_CLUSTER_RAW% %DOWNSTREAM_PEER_CHAIN_FINGERPRINTS_256%, and %DOWNSTREAM_PEER_CHAIN_SERIALS%) as well as significant boosts to json parsing.  See release notes for details
• Added support for %BYTES_RECEIVED%, %BYTES_SENT%, %UPSTREAM_HEADER_BYTES_SENT%, %UPSTREAM_HEADER_BYTES_RECEIVED%, %UPSTREAM_WIRE_BYTES_SENT%, %UPSTREAM_WIRE_BYTES_RECEIVED% and access log substitution strings for UDP tunneling flows.
• Added ECDS support for UDP session filters.

Docker images: https://hub.docker.com/r/envoyproxy/envoy/tags?page=1&name=v1.32.0 Docs: https://www.envoyproxy.io/docs/envoy/v1.32.0/ Release notes:

https://www.envoyproxy.io/docs/envoy/v1.32.0/version_history/v1.32/v1.32.0 Full changelog: envoyproxy/envoy@v1.31.0...v1.32.0

Signed-off-by: Alyssa Wilk alyssar@chromium.org

Changelog

Sourced from github.com/envoyproxy/envoy's changelog.

Release Process

Active development

Active development is happening on the main branch, and a new version is released from it.

Stable releases

Stable releases of Envoy include:

• Major releases in which a new version a created directly from the main branch.
• Minor releases for versions covered by the extended maintenance window (any version released in the last 12 months).
  • Security fixes backported from the main branch (including those deemed not worthy of creating a CVE).
  • Stability fixes backported from the main branch (anything that can result in a crash, including crashes triggered by a trusted control plane).
  • Bugfixes, deemed worthwhile by the maintainers of stable releases.

Major releases happen quartely and follow the schedule below. Security fixes typically happen quarterly as well, but this depends on the number and severity of security bugs. Other releases are ad-hoc and best-effort.

Security releases

Critical security fixes are owned by the Envoy security team, which provides fixes for the main branch. Once those fixes are ready, the maintainers of stable releases backport them to the remaining supported stable releases.

Backports

All other security and reliability fixes can be nominated for backporting to stable releases by Envoy maintainers, Envoy security team, the change author, or members of the Envoy community by adding the backport/review or backport/approved label (this can be done using [repokitteh]'s /backport command). Changes nominated by the change author and/or members of the Envoy community are evaluated for backporting on a case-by-case basis, and require approval from either the release manager of stable release, Envoy maintainers, or Envoy security team. Once approved, those fixes are backported from the main branch to all supported stable branches by the maintainers of stable releases. New stable versions from non-critical security fixes are released on a regular schedule, initially aiming for the bi-weekly releases.

Release management

Major releases are handled by the maintainer on-call and do not involve any backports. The details are outlined in the "Cutting a major release" section below. Security releases are handled by a Release Manager and a Fix Lead. The Release Manager is responsible for approving and merging backports, with responsibilties outlined in https://github.com/envoyproxy/envoy/blob/main/BACKPORTS.md. The Fix Lead is a member of the security team and is responsible for coordinating the overall release. This includes identifying issues to be fixed in the release, communications with the Envoy community, and the

... (truncated)

Commits

• 86dc7ef repo: Release v1.32.0 (#36597)
• 9c75441 fix potential null dereference in ext_authz (#36268)
• 5b0d56d tcp_proxy_protocol: reduce stats contention by moving the stats to factory (#...
• 440708f deps/cel: Resolve compiler warnings (#36590)
• 87f3921 deps/protoprocess: Resolve compiler warnings (#36568)
• e52de81 docker/release: Update Ubuntu image -> 58b8789 (#36591)
• eabfe54 docs: summary (#36596)
• 97a2f28 release: Changelog cleanups (#36595)
• e8abd86 build(deps): bump envoyproxy/toolshed from actions-v0.2.36 to 0.2.37 (#36593)
• cbfd43b build(deps): bump google.golang.org/protobuf from 1.34.2 to 1.35.1 in /contri...
• Additional commits viewable in compare view

Updates google.golang.org/protobuf from 1.34.2 to 1.35.1

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions