HTTPRoute extraRules inherit matches/filters from previous rules

The operator renders spec.httpRoute.extraRules incorrectly when a CR defines multiple rules.

Example input:

spec:
  httpRoute:
    parentRefs:
      - name: example-gateway
    hostnames:
      - example.com
    extraRules:
      - matches:
          - path:
              type: PathPrefix
              value: /a
        filters:
          - type: RequestHeaderModifier
            requestHeaderModifier:
              add:
                - name: x-scope
                  value: "a"
      - matches:
          - path:
              type: PathPrefix
              value: /b

Expected behavior

spec.rules[1] contains only the second match (/b) and no filters.

Actual behavior

spec.rules[1] contains the second match (/b) plus the filters from the first rule (x-scope: a). If the second entry omits matches, it also keeps the first entry's matches.

Start at the HTTPRoute rendering path for spec.httpRoute.extraRules and reproduce the supplied CR example. Verify that each rendered rule uses only its own matches and filters, including when either field is omitted; done means later rules no longer inherit fields from earlier rules.