Update envoy-gloo to 1.32.3-patch2

[ashishb-solo]

Description

Update envoy-gloo dependency to v1.32.3-patch2

API changes

N/A

Code changes

None

CI changes

None

Docs changes

None

Context

Interesting decisions

Testing steps

Notes for reviewers

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

BOT NOTES:
resolves https://github.com/solo-io/solo-projects/issues/7608

[github-actions]

Visit the preview URL for this PR (updated for commit 6c368f1):

https://gloo-edge--pr10595-envoy-1-32-bump2-mp52gjr2.web.app

_{(expires Wed, 19 Feb 2025 06:28:40 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 77c2b86e287749579b7ff9cadb81e099042ef677}

[solo-changelog-bot]

Issues linked to changelog:
https://github.com/solo-io/solo-projects/issues/7608

[nfuden]

Can we please add something to the changelog for customers to address

http: The default configuration of Envoy will continue to trust internal addresses while in the future it will not trust them by default. If you have tooling such as probes on your private network which need to be treated as trusted (e.g. changing arbitrary x-envoy headers) please explictily include those addresses or CIDR ranges into [internal_address_config](https://www.envoyproxy.io/docs/envoy/v1.32.3/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto.html#envoy-v3-api-field-extensions-filters-network-http-connection-manager-v3-httpconnectionmanager-internal-address-config) See the config examples from the above internal_address_config link. You can turn up or test the upcoming internal address defaults by setting runtime guard envoy.reloadable_features.explicit_internal_address_config to true.

[nfuden]

Please add a link to enterprise showing it passing as well so we dont block other developers from updating oss