fold "routing" package into main package

there was no reason to have separate package,
it was only annoying
split Routes & Route up into Table, Route and Destination

note that Destination is the exact same thing as what a Route was.
It's the thing that sends data to one tcp endpoint, with spooling etc.
This commit is mostly just renames.
The Table is the global structure containing a list of Routes,
and Routes is basically a list of Endpoints.
define initial routing in cfg imperatively

after some more code cleanup, this should allow for less code,
because we can reuse the imperative command handling of the telnet admin
inputs.
the old way of declaratively defining the desired state requires more
structs and data juggling.
It's possible that I'm wrong about this and we'll revert back, but we'll
see.
shorter name for statsd object, gofmt
updates for imperative; gofmt
add imperative code, switch telnet handler to it
put telnet interface in separate file
bettor organisation + fixes

* admin_telnet needs routes which resulted in circular import
* since we use separate files, no need for anything more complicated
  -> all main carbon-relay-ng stuff is pretty tightly coupled, so
     let's just put in main package
* name the two admin interfaces more alike
* move the telnet muxer (similar to net/http) into a clearer file.
update people on whats going on
organize the 3 routing structures in their own files
fixfixfix
fixfix2

make it compile, other than the admin interfaces.
fix up command parsing for the most part
make Matcher type for nice matching, part of blacklist, route and destination
remove 'key' from destination, it seems only useful for routes
better variable names here and there (pattern -> regex, ch -> In)
remove first_only
fixes for blacklist, dispatching, etc

make blacklist part of table, so it's easier to modify
simplify table Dispatching, no need for sync channel
some other fixes
work on table operations and updating admin http
fixes, var cleanups, route relaying, telnet view
disable a few methods that I haven't figured out yet
work wrt destination relay

use buffered connection for faster writes, with flushing
refactor/improve destination relay code, non-blocking see #34 (WIP)
move out pickle and conn code
add matcher code (oops)
Matcher updating for route/dest & locking
non-blocking conn and spool writes