Dapr & NGINX ingress controller best practices

**What content needs to be created or modified?**
A common architectural pattern is to deploy an ingress controller such as NGINX with a Dapr sidecar alongside it. This is beneficial as it allows exposing the Dapr APIs beyond a single cluster and allows features such as Dapr's distributed tracing to show end-to-end request data among other things.

There are multiple blogs on configuring this:
- https://alphatango086.medium.com/nginx-ingress-controller-with-dapr-a69e03e98209
- https://dev.to/stevenjdh/create-a-kubernetes-nginx-controller-with-dapr-support-3e8n
- https://carlos.mendible.com/2020/04/05/kubernetes-nginx-ingress-controller-with-dapr/

**Describe the solution you'd like**
The Dapr docs should standardize on the recommended way to deploy Dapr alongside NGINX ingress controller and create a "How-to" article on it.

**Where should the new material be placed?**
A couple of options but likely it should be placed under the Kubernetes documentation: https://docs.dapr.io/operations/hosting/kubernetes/

Alternatively, it could be placed under integrations as that is where KEDA lives: https://docs.dapr.io/developing-applications/integrations/

**The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos**

**Additional context**