Feature disparity between gRPC bridge and gRPC reverse bridge

*Title*: *Feature disparity between gRPC bridge and gRPC reverse bridge*

*Description*:

Currently there's a bit of config/feature disparity between these 2 filters, where the reverse bridge offers more functionality. It would be great to support the same config options in the gRPC bridge as well. For example bridging a `application/x-protobuf` HTTP 1.1 request without the gRPC header frame and responding with the same content type and without the gRPC header frame.