admin(eggs): add `force_outgoing_ip` option

[matthewpi]

Requires https://github.com/pterodactyl/wings/pull/135

Closes #3841

[parkervcp]

I feel like having your traffic use the expected ip is the only way to go here and not making it an option.

[matthewpi]

I feel like having your traffic use the expected ip is the only way to go here and not making it an option.

The problem is you lose internal container networking when this feature is enabled. The way the feature works is best described by the Wings PR; it creates a dedicated network per-server with the host_ipv4 option, which is the only way setting the correct outgoing IP seems to work (at least when using Docker). I previously explored having both a dedicated network for outgoing traffic and one for internal traffic, but it is either not currently possible or requires a very specific configuration in order to work correctly.

[parkervcp]

Okay. So it's a double edged sword. On one hand you get the outbound correct. On the other you lose internal networking.

A good callout.