Add support for X-Azure-FDID as a UseForwardedHeaders "Known Proxy"

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Is your feature request related to a problem? Please describe the problem.

I am trying to use UseForwardedHeaders in an app behind Azure Front Door, but the remote ip address received on the application is random. The only options I see right now are to either restrict known networks to a class B (147.243.x.x based on observations) or remove all known proxies from the configuration. Basically, drastically reduce security or remove it completely.

### Describe the solution you'd like

A great feature would be to configure ForwardedHeadersOptions with an expected header and value as an alternate security mechanism to remote ip address.

Ex. options.KnownHeaders.Add("X-Azure-FDID", "55ce4ed1-4b06-4bf1-b40e-4638452104da");

### Additional context

_No response_