Exceeding Max STREAM ID should be a connection error

[ianswett]

In most places in QUIC, if an error is clearly avoidable(ie: only a buggy implementation would do so), then we advise closing the connection with an error, not just closing the stream with an error.

In section 4.5 of transport(https://tools.ietf.org/html/draft-ietf-quic-transport-20#section-4.5) it says:
"Endpoints MUST NOT exceed the limit set by their peer. An endpoint
that receives a STREAM frame with a stream ID exceeding the limit it
has sent MUST treat this as a stream error of type STREAM_LIMIT_ERROR"

Came up in discussion of #2730

[ianswett]

As I commented in the updated PR description, section 19.11 already says this:
"An endpoint MUST terminate a connection
with a STREAM_LIMIT_ERROR error if a peer opens more streams than was
permitted."

[martinthomson]

Reopening to keep this visible.

[mnot]

#2826 is effectively the proposal, correct?

[martinthomson]

Yes. It was editorial. So I merged it. But then this issue really isn't editorial.

[ianswett]

Yes, I opened this issue, then found that text in section 19.11 in the doc said exceeding MAX_STREAM_ID was a connection error, so the PR ended up aligning the two sections.