Reject unsupported resources when expression router enabled and attach translationError events

[randmonkey]

Is there an existing issue for this?

• I have searched the existing issues

Problem Statement

Because Kong does not support stream proxies when expression router enabled, we could not support the following kubernetes resources when ExpressionRoutes enabled:
TCPIngress, UDPIngress, TCPRoute, UDPRoute, TLSRoute
Also, we intentionally dropped support of the following resources:
kantive.Ingress, networking.k8s.io/v1beta1.Ingress,extensions/v1beta1.Ingress.
To prevent them from generating traditional routes that will pollute the whole kong configuration, we need to disable their translation and attach a TranslationError event to them.

Proposed Solution

• Attach TranslationError event to the unsupported objects in parser if ExpressionRoutes is enabled

Additional information

No response

Acceptance Criteria

• The unsupported resources does not get translated to kong configurations when ExpressionRoutes enabled.
• TransalationError type events are attached to unsupported resources.