lb: hash policy support in the hash lb (#39505)

Commit Message: api: add hash policy to hash lb configuration
Additional Description:

> Now, the hash policy (header, cookie, source ip, etc.) is part of the
route entry. But in actual practices, almost all well known control
planes (istio, gloo, envoy gateway, etc) make the hash policy be part of
upstream configurations (like destination rule of istio).
> Route level hash policy not only bring compleixty of control plane
developing, but make it's weird to configure multiple upstreams route
with these control plane.
> For example, given single route with two different upstreams that has
different hash policies in the control plane, how control plane convert
them to the envoy configuration?

Address [#39502](envoyproxy/envoy#39502)

Risk Level: low, api only.
Testing: n/a.
Docs Changes: n/a.
Release Notes: n/a.
Platform Specific Features: n/a.

---------

Signed-off-by: wangbaiping(wbpcode) <[email protected]>

Mirrored from https://github.com/envoyproxy/envoy @ 68998d38e5b084aa2af657bba1bed873f9de270f

Author: update-envoy[bot]

envoy/extensions/load_balancing_policies/common/v3/BUILD

@@ -8,6 +8,7 @@ api_proto_package(
     deps = [
         "//envoy/annotations:pkg",
         "//envoy/config/core/v3:pkg",
+        "//envoy/config/route/v3:pkg",
         "//envoy/type/v3:pkg",
         "@com_github_cncf_xds//udpa/annotations:pkg",
     ],

envoy/extensions/load_balancing_policies/common/v3/common.proto

@@ -3,6 +3,7 @@ syntax = "proto3";
 package envoy.extensions.load_balancing_policies.common.v3;
 
 import "envoy/config/core/v3/base.proto";
+import "envoy/config/route/v3/route_components.proto";
 import "envoy/type/v3/percent.proto";
 
 import "google/protobuf/duration.proto";
@@ -136,4 +137,10 @@ message ConsistentHashingLbConfig {
   // This is an O(N) algorithm, unlike other load balancers. Using a lower ``hash_balance_factor`` results in more hosts
   // being probed, so use a higher value if you require better performance.
   google.protobuf.UInt32Value hash_balance_factor = 2 [(validate.rules).uint32 = {gte: 100}];
+
+  //  Specifies a list of hash policies to use for ring hash load balancing. If ``hash_policy`` is
+  // set, then
+  // :ref:`route level hash policy <envoy_v3_api_field_config.route.v3.RouteAction.hash_policy>`
+  // will be ignored.
+  repeated config.route.v3.RouteAction.HashPolicy hash_policy = 3;
 }