IPv6 address literals are not handled well

[thwarted]

If the servers config option includes IPv6 address literals like '[::1]:11300' or [fe80::800:27ff:fe00:0%eth0]:11300, beanstalk_console can not connect. This is because BeanstalkInterface __construct is naive in parsing the server address. I hacked up a serious kludge to take the last element of the exploded result as the port, to verify that it would work, but that code is too ugly to productionize.

It may be better to take URL-like values as the server list, like beanstalk://host:port/ (this is what the backburner library does. Then parse_url can be used to extract the necessary components unambiguously. Maybe maintain backwards compatibility by using parse_url if the string starts with beanstalk://?

Note that it has no trouble connecting over IPv6 if the address or name can be parsed correctly (specifically, giving a name that only resolves to an IPv6 address or AAAA records does work).