switch to `draft connect` for the ingress parts?

[bacongobbler]

Due to the complexity of the setup, ingress support in draft was removed in favour of draft connect (see Azure/draft#573). In 0.12.0 and above, it's recommended in the documentation to use draft connect as it initiates a tunnel straight to all the pods without needing to set up ingress controllers, DNS, etc. Are there plans to eventually migrate over, or are there limitations with the current system?

[sabbour]

Part of the demo is to show HTTP Application Routing so it depends on what we want to show here? cc @bradygmsft

[bradygmsft]

@bacongobbler this is an interesting request. As @sabbour calls out we do want to demonstrate the AKS Http App Routing capabilities and features so I think it'll remain as-is. However, I would be interested to know the implications of both approaches, what @squillace thinks, too. Also cc @gabrtv as I'd be curious his perspective on this. You all know I'm learning the K8s arts, still in my infancy stages of it, so I'm eager to hear your collective perspective on what we should do here. I'd prefer to optimize for the Http App Routing feature, but I'm open to ideas.