feat(kuma-dp): rework on the virtual probes to support probing tcp and grpc ports

[jijiechen]

Checklist prior to review

Implements this MADR: gRPC and TCP probes

• Link to relevant issue as well as docs and UI issues
  • fixes Support TCP and grpc liveness probes #3875
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
• Tests (Unit test, E2E tests, manual test on universal and k8s)
  • tested with unit and manual tests
  • Don't forget ci/ labels to run additional/fewer tests
• Do you need to update UPGRADE.md? --
  • No, it's compatible
• Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label)
  • No

Changelog: feat(kuma-dp): support TCP and gRPC probes for data planes running on Kubernetes

[jijiechen]

Hi reviewers, sorry that this is a large PR. To help you review the code easily, let me explain what are included in this PR.
This PR basicly refactors the existing HTTP-only "virtual probes" and implements the new model of "virtual probe" that support all three kinds of pod probes: TCP, gRPC and HTTP.

Here are the break down tasks:

1. introduce a new component into kuma-dp to start the virtual probe server, it's an HTTP server. This is placed at directory app/kuma-dp/pkg/dataplane/probes
2. configure kuma-dp from the injector.go to run the virtual probe server according to user's auto-injector configuration
3. in the function of OverridePodProbes that is called by injector.go, change the existing virtual probe overriding to support all the three kinds of probes
4. exclude the virtual probe server port on the ways of settings of transparent proxy:
   1. kuma-sidecar: PodRedirect in file pkg/transparentproxy/kubernetes/kubernetes.go
   2. kuma-cni: NewIntermediateConfig in file app/cni/pkg/cni/annotations_linux.go

[jijiechen]

The PR also includes some minor/revelant refactorings.

Here are some of them:

1. Removed Probes to be on dataplane objects sinec we don't generate an insecure listener for the virtual probes server any more. So I removed this field and its message definition.
2. Removed grpc health check proto files from the repo and use the package from GitHub since it was included in the testserver package previously and if I introduce the same proto into a package under kuma-dp, it will generate a conflict panic.
3. Added the capabilities of supporting scheme and httpHeaders for HTTP probes, supporting of timeout is added for all three kinds of probes.

[jijiechen]

According to recent review suggestions, here are the latest changes:

1. Introduced a new concept of "application probe proxy", and corresponding annotations/configurations
2. Brought back previous versions of "virtual probes"
3. Built the compatibility of using "virtual probes" by disabling "application probe proxy"
4. Marked "virtual probes" related annotations as Deprecated

Basically, the idea is, "application probe proxy" will be enabled defaultly and it's successor of "virtual probes".
User can still use "virtual probes" by disabling "application probe proxy" (set the port to 0)
When virtual probes are previously disabled using CP configuration or pod annotations, "application probe proxy" will also be disabled defaultly.