Kubernetes NuGet Packaging

[karelz]

Discussed in https://github.com/microsoft/reverse-proxy/discussions/1631

^{Originally posted by @dpbevin April 3, 2022} Several people have expressed the desire to consume the Kubernetes YARP via NuGet packages. As of 3-April-2022, there are seven different C# projects (in this repo) that comprise the Kubernetes support for YARP.

Proposal

I'm proposing that we collapse these seven projects into a single project before considering NuGet packaging for the Kubernetes support.

There may also be an opportunity to simplify the generalized "OperatorFramework" code as part of the process and make the code more specific to the job at hand.

@specialforest @MihaZupan

[karelz]

Triage: We believe that collapsing makes sense (incl. @MihaZupan's opinion as our top expert on k8s :))

[dpbevin]

First PR is ready to roll - this just removes deps and moves the necessary pieces of code around.

I have a follow-up commit ready for a separate PR that cleans up namespaces. I imagine those changes will need a bit more discussion.

[danielkatz]

Is there any progress done in this area?

[acortelyou]

@MihaZupan Can we consider official nuget packaging now that the project structure has been updated? There are many duplicate requests for this as well as considerable confusion identifying the correct daily builds to use. At least lets get it on a roadmap.