IBodyProducer isn't supported with twisted wsgi stacks

[Robert Collins]

U1, which would like to use oops-wsgi in a twisted wsgi stack, have an extension where they can return an IBodyProducer rather than a generator, which gets put back into the event loop rather than tying up a thread. That is interfered with by the OOPS middleware as it currently stands.

[Robert Collins (lifeless)]

This is I think the needed contract:
 - app() returns something
 - headers may or may not have been sent
 - that thing is direct-iterable or async iterable via IBodyProducer
 - we want to run some oops-wsgi code when:
  - first bytes are gotten (unbuffer headers, timeout based oopses)
  - end of stream (unbuffer headers)
  - an exception is raised (but not in the gateway code)
    - if nothing has been sent this will want to inject/return data.

So we need a parameterisable wrapper for the result from app()
And a small number of callbacks (3) which the wrapper needs to reliably call
I will start by refactoring oops-wsgi itself to have the needed extension point and this structure internally. Then will write an IBodyProducer wrapper. Then we see how badly I messed it up:)

[Robert Collins (lifeless)]

oops-wsgi 0.0.6 should be hookable enough.