chore(MeshHTTPRoute): default catch all path in route match

[bartsmykla]

According to Envoy docs, match must have precisely one of prefix, path, safe_regex, connect_matcher, path_separated_prefix, path_match_policy set, so when policy doesn't specify explicit type of matching, we are assuming "catch all" path (any path starting with "/").

Closes: #6758

Checklist prior to review

• Link to relevant issue as well as docs and UI issues
  • MeshHTTPRoute configuration fails in Envoy #6758
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS
  • It won't
• Tests (Unit test, E2E tests, manual test on universal and k8s)
  • Updated golden files for unit tests
• Do you need to update UPGRADE.md?
  • There is no need
• Does it need to be backported according to the backporting policy?
  • There is no need
• Do you need to explicitly set a > Changelog: entry here or add a ci/ label to run fewer/more tests?

Changelog: fix(MeshHTTPRoute): assume default catch all path (any path starting with "/") in route match when not explicitly set