func kubernetes deploy generates default readiness/liveness probes without warning

Scenario:

I create a single dotnet project with an event hub trigger and try to deploy it with "func kubernetes deploy" -- this will appear to succeed but will ultimately fail because k8s will try to probe the deployment for readiness/liveness, and since nothing is listening, it will kill the pod.

suggestion:

- liveness/readiness probe should be explicit *opt-in* only
- if opting in, allow specifying port and endpoint, as it currently defaults to / and port 80.

Start at the func kubernetes deploy entry point and reproduce the event hub trigger scenario. Inspect how Kubernetes readiness and liveness probes are generated, then verify the expected behavior for opt-in probes and configurable port and endpoint settings. Done means deployments without an HTTP listener no longer fail because of implicit probes.

Written by the indexing model from the issue text.