X-Forwarded-for should be marked as requirement for configuring Ops manager in High Availability

Hello Team,

Context: Customer is facing issue while configuring the Ops Manager in HA(High Availability) using Load Balancer. He is using Layer-4 LoadBalancer which do not support X-Forwarded headers. 

Blocker: The X-Forwarded-for is not mentioned as requirement on our documentation  page https://docs.opsmanager.mongodb.com/current/tutorial/configure-application-high-availability/#multiple-application-servers , due to which his Ops Manager HA is not able to identify source IP. In his words: 

_{"mentioned" != "MUST BE CONFIGURED ON LOAD BALANCER".}

_{that's the reason I raised this ticket for mongo support. we missed it because it wasn't clearly described as a requirement. And, as a result, HA does not work properly.}

--Another point he has mentioned in his comment is that why we are relaying on non-MongoDB customer headers, why not create mongodb specific custom HTTP header for source IP of automation agent like we are using for MongoDB Service version below: 

_{^{< X-MongoDB-Service-Version: gitHash=980038b07091a533affeaca3452736391c0df9f7; versionString=4.4.17.100.20210901T1617Z}}--

Is it possible to mark X-forwarded-for as requirement for configuring the OPS Manager in HA ?