Ingress canary header routing works for HTTP but gRPC requests ignore the split and all traffic stays on stable

The progressive delivery rule appears valid, but the gRPC path follows a different routing evaluation than the header-based HTTP test path.