k8s gateway extensions: allow customizing translator

[stevenctl]

Description

API changes

The only API is an internal code API to allow GME to take control of the Gateway translation.

Changed CreatePluginRegistry to GetPluginRegistry. AFAICT there is no need to recreate the registry each time but I can rever tthis if needed.

	// GetPluginRegistry exposes the plugins supported by this implementation.
	GetPluginRegistry() registry.PluginRegistry

Added: GetTranslator to allow conditionally switching the translation logic based on the type of gateway.

	// GetTranslator allows an extnsion to provide custom translation for
	// different gateway classes.
	GetTranslator(*apiv1.Gateway) translator.K8sGwTranslator

Context

See slack conversation here

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• [] I have added tests that prove my fix is effective or that my feature works

[github-actions]

Visit the preview URL for this PR (updated for commit a4ac9a2):

https://gloo-edge--pr9471-stevenctl-allow-cust-yvxfx2b9.web.app

_{(expires Tue, 02 Jul 2024 18:55:25 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 77c2b86e287749579b7ff9cadb81e099042ef677}

[jenshu]

should this take in the GatewayClass instead?

[stevenctl]

It leaves some flexibility to look at labels/annotations if needed. I'm not sure further restricting it gives much of an advantage.

[EItanya]

Changes LGTM, just want confirmation about the registry creation semantics for portal

[EItanya]

@jmhbh or @ilackarms would know better if this needs to be created every time, I don't think so but I defer to them.