Add support Hostname and Path rewrite in GatewayRoute

[cgchinmay]

Is your feature request related to a problem?
AppMesh API will be adding support to the GatewayRoute which will allow customers to control the default Hostname rewrite and also modify the matched path URL. In addition there will be support for query_parameters based matching.
For more details:
aws/aws-app-mesh-roadmap#73

Describe the solution you'd like
AppMesh Controller CRD for GatewayRoute must be updated to allow customers to utilize this feature.

Note: Path rewriting requests is not valid (grpc/grpc-dotnet#110) in GRPC
Following are the expected changes to the GatewayRoute CRD

apiVersion: appmesh.k8s.aws/v1beta2
kind: GatewayRoute
metadata:
 name: SampleGatewayRoute
 namespace: my-gateway-route-ns
spec:
  awsName: SampleGatewayRoute_my-gateway-route-ns
  #HTTP Gateway Route
  http:
    match:
      # Only one of prefix or path can be specified
      prefix: "/" #Optional string
      path: #Optional
        #Only one of exact or regex can be specified
        exact: "/path" #Optional String
        regex: "regex", #Optional String
      query_parameters: #Optional
        - name: "query_field" #Required String
          match: #Optional
            exact: "value" #Optional String
    action:
      rewrite: #Optional
        prefix: "/rewrittenUri/", #Optional String.
        path: #Optional
          exact: "/rewrittenPath" #Optional String
        hostname: #Optional
          auto_hostname: "enabled" #Optional String. Allowed values are enabled/disabled.
      target: 
        ...
        
  #HTTP2 Gateway Route
  http2:
    #Same as HTTP Gateway Route
    
  #GRPC Gateway Route
  grpc:
    match:
      ...
    action:
      rewrite: #Optional
        hostname: #Optional
          auto_hostname: "enabled" #Optional String. 
      target: 
        ...
-------

[cgchinmay]

Fixed with v1.4.0