(feat) Only respond with raw messages
(refac) Introduced middleware for outbound data

That is, we have a middleware that can manipulate
responses from irc -> the webirc client

Next step is to extend functionality for adding a
middleware for inbound data
(refac) Added Middleware for inbound messages

May reconsider the interface for adding in- and outbound
middleware. The current interface is useIn and useOut
respectively.

Next, I do want to specify what irc "container" to use
in the middleware. As it is specified on proxy init time.
Somehow I do want the "containers" to be added to the
request and used later on, if no container is found we can
default the one we are currently using.
(chore) Running traceur for ES6 comability

Why write function everytime when you don't have to
(refac) Renamed and moved code
(feat) useContainer do define what connection container to use

Instead of using a middleware I wrote about in an earlier
commit, I opted for just using an expressive method
useContainer(containerObj) instead.

I think this will cause less confusion and it is easy to
spot what connection is used.