[feat gw-api] implement grpcroute match

[shuqz]

Description

• implement grpcroute match

• refactor code in rule precedence file, the big changes are

  • grpcroute and httproute has independent compare precedence logic
  • the sort logic will take all routes from same port but it will sort grpcroute and httproute independently, and append them together. based on current logic, rules from httproute will be appended first since they tend to be more specific, but we might plan to have it configurable by user later. This is to handle the case when both grpcroute and httproute attached to same port, and for old logic, if will try to compare a rule from grpcroute and a rule from httproute, which does not make sense since they are different. Also, because the only time both can be attached is when hostname does not overlap, so they will never have same routing rule. we just need to keep the relative priority within each route to be correct.

• change priority of prefix and regex for easy of comparison, before it is exact > regex > prefix, now it is exact > prefix > regex (align with ingress)

• did not add e2e test yet, did manual testing and run some existing e2e test

Checklist

• Added tests that cover your change (if possible)
• Added/modified documentation as required (such as the README.md, or the docs directory)
• Manually tested
  tested with 2 yaml files below

  rules:
    - matches:
        - method:
            # provide only method
            method: User
        - headers:
            # no method provided, will be treated as /*
            - name: test-header-4
              value: test-value-4
      backendRefs:
        - name: echoserver3
          port: 80
    - matches:
        - method:
            # provide both service and method
            service: com.example
            method: Login
          headers:
            - name: test-header-1
              value: test-value-1
            - name: test-header-2
              value: test-value-2
        - method:
            # provide only service
            service: second.com
          headers:
            - name: test-header-3
              value: test-value-3
-----------------------------------
  rules:
    - matches:
        - method:
            # provide only method
            type: RegularExpression
            method: User*
          headers:
            - name: test-header-5
              value: test-value-5
        - method:
            # provide only service
            type: RegularExpression
            service: service?
          headers:
            - name: test-header-6
              value: test-value-6

result:

• Made sure the title of the PR is a good description that can go into the release notes

BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯

• Backfilled missing tests for code in same general area 🎉
• Refactored something and made the world a better place 🌟

[shraddhabang]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: shuqz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[shuqz]

/retest

[shraddhabang]

/retest

[shraddhabang]

/lgtm