feat(expression router) Implement translator of ingresses

[randmonkey]

What this PR does / why we need it:

• add feature gate ExpressionRoutes and flags in related structures (KongClient,Parser,KongState,Route) to process expression based routes in a different way
• Implement translation of ingresses
• Add integration tests for expression based router

Which issue this PR fixes:

fixes #3750

Special notes for your reviewer:

PR Readiness Checklist:

Complete these before marking the PR as ready to review:

• the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

[codecov]

Codecov Report

Patch coverage: 78.2% and project coverage change: +0.4 🎉

Comparison is base (ee30642) 58.7% compared to head (440d449) 59.1%.

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #3935     +/-   ##
=======================================
+ Coverage   58.7%   59.1%   +0.4%     
=======================================
  Files        141     142      +1     
  Lines      16252   16521    +269     
=======================================
+ Hits        9545    9772    +227     
- Misses      6055    6085     +30     
- Partials     652     664     +12     

Impacted Files	Coverage Δ
internal/dataplane/parser/parser.go	73.4% <0.0%> (+0.3%)	⬆️
internal/manager/utils/kongconfig/root.go	50.3% <46.6%> (+0.3%)	⬆️
internal/dataplane/kong_client.go	65.3% <60.0%> (+3.4%)	⬆️
internal/manager/run.go	37.1% <61.5%> (+1.0%)	⬆️
internal/dataplane/kongstate/route.go	89.1% <76.9%> (-2.5%)	⬇️
internal/dataplane/parser/translate_ingress.go	91.4% <77.4%> (-1.8%)	⬇️
internal/dataplane/deckgen/generate.go	31.4% <77.7%> (ø)
...ternal/dataplane/parser/translators/ingress_atc.go	88.3% <88.3%> (ø)
internal/annotations/annotations.go	97.4% <100.0%> (+<0.1%)	⬆️
internal/dataplane/parser/translators/ingress.go	94.1% <100.0%> (+0.1%)	⬆️
... and 1 more

... and 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[czeslavo]

That's a lot of good work! 👍

My comments mainly gravitate around my thought that we should be careful when adding such a volume of brand new code by making sure that all of the pieces we add are properly unit tested + we have at least one integration test covering it works with Kong as expected in a sunny day scenario.

[randmonkey]

That's a lot of good work! +1

My comments mainly gravitate around my thought that we should be careful when adding such a volume of brand new code by making sure that all of the pieces we add are properly unit tested + we have at least one integration test covering it works with Kong as expected in a sunny day scenario.

I added several unit tests fro translating ingresses to expression routes. For integration tests, I added workflow integartion-tests/dbless-expression-router to run integration tests that are valid using expression routes. tests using TCPIngress,UDPIngress,TCPRoute,HTTPRoute,GRPCRoutes and knative.Ingress are skipped. Also, the case testing HTTP redirect is skipped because Kong gateway does not support this when using expression router.

[pmalek]

[czeslavo]

🎉