Update Allocation fields to allow ipv4 and ipv6 #428

[notAreYouScared]

@RMartinOscar Have you tested this with wings? Do IPv6 Allocations correctly translate into wings and get assigned to servers? I don't do much of anything with IPv6 so my knowledge is limited...

@iamkubi anything on the wings side that this might break?

Below is what I encountered. No idea if I got the right ipv6.

ERROR: [Jun 25 22:50:05.732] encountered error processing a server power action in the background action=start error=environment/docker: failed to start container: Error response from daemon: driver failed programming external connectivity on endpoint 16cef740-3ebe-4432-bb08-36b574b9ca34 (1f4e38f4ffb3b47f4f98a4e996708627cdcc3fed1ccae36be7bd1ffd687895cf): failed to bind port fe80::5054:ff:fef6:255c:25565/tcp: Error starting userland proxy: listen tcp6 [fe80::5054:ff:fef6:255c]:25565: bind: invalid argument server_id=16cef740-3ebe-4432-bb08-36b574b9ca34

Stacktrace:
Error response from daemon: driver failed programming external connectivity on endpoint 16cef740-3ebe-4432-bb08-36b574b9ca34 (1f4e38f4ffb3b47f4f98a4e996708627cdcc3fed1ccae36be7bd1ffd687895cf): failed to bind port fe80::5054:ff:fef6:255c:25565/tcp: Error starting userland proxy: listen tcp6 [fe80::5054:ff:fef6:255c]:25565: bind: invalid argument
environment/docker: failed to start container

[lancepioch]

We do not support ipv6 at all or at any level afaik. This is something at the bottom of the backlog.