Fix bug in HTTP/2 outbound flow control

Motivation:

The outbound flow controller logic does not properly reset the allocated
bytes between successive invocations of the priority algorithm.

Modifications:

Updated the priority algorithm to reset the allocated bytes for each
stream.

Result:

Each call to the priority algorithm now starts with zero allocated bytes
for each stream.
Seems like we are doing DFS. Should we be doing a BFS?  I'm not sure if this changed but just a general thought.  I can't find explicit guidance in the spec but seems like elements closer to the root are higher "priority"?