expose callback in HttpObjectAggregator for handling oversized messages

Use case: in some situations I just want to catch an exception, in others I want to return a `413` and close straight away. In others I want to return a `413`, close the incoming connection but still forward the partial message down the pipeline.

If there's a less obtrusive way of reacting to oversize messages I'd take it :)