add option to enable x-forwarded-for header for gateways

#### Feature Description

consul version: v1.8.3

Needs an option to enable the `use_remote_address` option when setting up http listener for envoy ingress gateway.
According to envoy docs:
```
In general, use_remote_address should be set to true when Envoy is deployed as an edge node (aka a front proxy), whereas it may need to be set to false when Envoy is used as an internal service node in a mesh deployment.
```

#### Use Case(s)

Need the option so that the service can get the real ip address of the requester.

#### Note

We are using consul ingress gateway feature in nomad: https://www.nomadproject.io/docs/job-specification/gateway#gateway-stanza, so this option probably needs to be surfaced there as well in order to be used.

Start by tracing the HTTP listener setup for the Envoy ingress gateway and the Consul ingress gateway configuration referenced by the Nomad gateway stanza. Confirm how an option can surface Envoy's use_remote_address setting and verify that the resulting service can receive the requester's real IP address.

Written by the indexing model from the issue text.