Adding window maintenance flag to HTTP/2 inbound flow control

Motivation:

Currently, window maintenance is automatically performed when a flow
control window drops below half its initial size. We should provide a
way for advanced applications to determine whether or not this should be
done on a per-stream basis.

Modifications:

Modifying DefaultHttp2InboundFlowController to allow enabling/disabling
of window maintenance per stream.

Result:

Inbound flow control window maintenance will be dynamically
configurable.
Do you need to initialize: window, lowerBound, or endOfStream?

This is a repeat but I don't think we discussed.
I still haven't quite figure out under which conditions github says a comment is out of data, but I think commenting on a line with no change is not a good idea (seems like the next push will mark it as outdated).