Lambda Ingress via Mesh Gateway Docs are Incomplete

#### Feature Description

[This Documentation](https://developer.hashicorp.com/consul/docs/lambda/invoke-from-lambda) is very robust, *except* for the configuration requirements of the mesh gateways.

As someone who uses Consul in a way that does not require mesh gateways for inter datacenter communications, I am not sure which configuration or `mode` to set my mesh gateways to, as it seems like `local` or `remote` would service my purpose.

I'm also not sure if I **need** the proxy default configuration proposed in [this document](https://developer.hashicorp.com/consul/docs/connect/gateways/mesh-gateway#enabling-gateways-globally) since I'm only deploying mesh gateways for the purpose of allowing lambda applications to communicate via service mesh.

Technically this is a documentation/information request, but feature request seemed to be the only issue option that was close to what I needed.

Edit: It would be helpful to understand why this would be a mesh gateway and not an ingress gateway for this functionality as well, since mesh gateways are for communication between datacenters, and ingress gateways are for routing traffic from outside a service mesh, to inside the service mesh

Start with the Lambda invocation documentation and the linked mesh gateway configuration documentation. Clarify the required gateway mode, whether the global proxy default is needed, and why this integration uses a mesh gateway rather than an ingress gateway. Done means the Lambda documentation answers each configuration question and explains the gateway choice.

Written by the indexing model from the issue text.