Migrating to gRPC stats filter for gRPC stats

*Title*: Will using gRPC stats filter in conjunction with gRPC bridge filter lead to twice the number of gRPC stats being emitted?

*Description*:
As of v1.12.0, "The use of [gRPC bridge filter](https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_http1_bridge_filter#config-http-filters-grpc-bridge) for gRPC stats has been deprecated in favor of the dedicated [gRPC stats filter](https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_stats_filter#config-http-filters-grpc-stats)." If we still use the gRPC bridge filter for bridging but want to use gRPC stats for stats now that telemetry from the bridge filter is considered deprecated, would it be safe to have both filters? I'm primarily concerned about stats duplication.