Allow updating connection limits dynamically

[zz85]

Problem:

Currently there's no way to update Limits from the limiter after connection is established.

One use case would to updating stream limits or send sizes after there's sufficient information about a connection like the intended server_name to start applying a different set of limits.

Solution:

An API to allow updating connection limits

Requirements / Acceptance Criteria:

Out of scope:

[camshaft]

It's unlikely we'll enable dynamic limits at arbitrary points in the connection lifecycle, as we quickly run into accounting issues. For example, what happens when the limits drop which causes the library or peer to violate them?

I think a good approach would allow the connection limiter to update the limits for the connection right before we create the application space. Things like server name and application protocol would be available at this point.