instrumentation: proxy the correct callback

Connect instrumentation wasn't proxying the correct callback, which
*should* have been the `next` continuation, but was intead the whole
middleware function, which is already being bound to scope elsewhere. In
the process of figuring this out, realized that one of my test cases was
very much incomplete, and completed it.
docs: updated for new version
release: 0.11.4