Feat: add HTTPRoute-rule name to envoy route metadata

[Ido-Itz]

This PR adds route rule names to the Envoy route metadata (section-name) as described in #4551

This will allow various runtime flows (such as access logging) to have awareness of the matched route-rule.

Fixes #4551

Release Notes: No

[lsjostro]

would this mean I can target a http route rule section with a securitypolicy?
like this?

apiVersion: gateway.envoyproxy.io/v1alpha1
kind: SecurityPolicy
metadata:
  name: ext-auth-foo
spec:
  targetRefs:
    - group: gateway.networking.k8s.io
      kind: HTTPRoute
      name: foobar
      sectionName: mainRule
  extAuth:
    grpc:
      backendRefs:
        - name: authserver
          namespace: authserver
          port: 8080

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (main@44408dd). Learn more about missing BASE report.
Report is 12 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4561   +/-   ##
=======================================
  Coverage        ?   65.58%           
=======================================
  Files           ?      211           
  Lines           ?    31951           
  Branches        ?        0           
=======================================
  Hits            ?    20955           
  Misses          ?     9754           
  Partials        ?     1242           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[guydc]

LGTM

[guydc]

would this mean I can target a http route rule section with a securitypolicy?

@lsjostro - not yet. That is being tracked here #4085

[Ido-Itz]

/retest

[zhaohuabing]

I didn't see the SectionName in the testdata outpout file. Did I miss anything?

[Ido-Itz]

You're right. I missed the scenario of matcher-less routes :p

[Ido-Itz]

Fixed the issue of routes with no matchers + added support for gRPC routes as well