allow channel to start with '&' as per rfc1459/1.3

this fixes some strange issues with weechat-otr and bitlbee which uses &foo-type channels generously.