Sort wildcard domain ingress routes after non-wildcard routes

[joelcox22]

I had a use-case where I wanted an ingress rule using a wildcard domain to act as a fallback when a more explicit rule did not exist, however with the sort logic of shortest hostnames first, the wildcard domain name was always taking priority even when a more specific domain name without a wildcard existed in a separate ingress route.

This change makes wildcard domains (e.g. *.example.com) be sorted after, and therefore take lower priority than non-wildcard domains (test.example.com), which seems to be a more sensible default behaviour to me.

If you'd like to test this, you can use the following helm values for now:

cloudflare-tunnel-ingress-controller:
  image:
    repository: ghcr.io/joelcox22/cloudflare-tunnel-ingress-controller
    tag: master-df3c2fb-amd64

Then deploy an ingress route with a wildcard, and you will see it's sorted in cloudflare connector application routes below the non-wildcard routes, where without this change, it ended up at the top of the list due to the hostname being shorter than the other routes that had more explicit domain names.

---

Note: these code changes and tests are generated by AI, but have been reviewed and tested by a human 😄

[joelcox22]

Updated sample values.yaml which can be used for testing this change with latest changes from this repo:

cloudflare-tunnel-ingress-controller:
  image:
    repository: ghcr.io/joelcox22/cloudflare-tunnel-ingress-controller
    tag: master-43cf4dd-amd64