New project direction regarding supported APIs

[shaneutt]

As a result of a community sync today (see #blixt in Kubernetes Slack for information on how to join these, we currently do them ad-hoc and vote on times in that channel) we've decided to change the official direction of the project significantly.

One of the original reasons why Blixt was created was to support the development of L4 in Gateway API. However over the years both TCPRoute and UDPRoute have become stagnant (due to lack of community interest in moving them forward) and it's unclear if they even belong in what has mostly become an L7 focused API. We've decided to divest ourselves from our previous goals related to driving L4 conformance in Gateway API and instead looking at a future where we explore L4 routing APIs on our own. As such the previous v0.5.0 milestone of Gateway API Conformance has been removed.

On this new path of exploration, we've agreed that the first step we want to take is to add initial support for the Kubernetes Service API, and in the future we think we may want to experiment with decomposing Kubernetes Services entirely. As such, you'll find that the goals in the README.md have been updated accordingly and we have a new v0.5.0 milestones for initial implementation of the Service API.