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.
It's just one array, so I'm not worried about the size ... especially since it's just a test.  Using the streamId as the index seemed simple enough.  The stream IDs are all created client side, so they will only be odd numbers: 3, 5, 7, etc.