User should be able to drop a path in the ingress level

## Describe the feature
Hello there,

Today, to drop a path, you need to implement a route that returns `404 http code status` when invoking your Knative service on that path. If you have configured scale to zero feature, this behaviour is not optimal as your pod will scale and you will be waiting for a few seconds (cold start time + time till your pod is in runnig state) for your path to be dropped.

I think we should be doing that in the ingress level without invoking the service

No file or test is named in the issue. Begin at the networking ingress entry points and compare current path handling with the scale-to-zero request flow; completion means the configured path is rejected at ingress without invoking or waking the service, with coverage for that behavior.

Written by the indexing model from the issue text.