feat(ext/fetch): Allow Response status 101

[ry]

Necessary for #13618

[piscisaureus]

Fails the following WPT tests:

  "/fetch/api/response/response-error.any.html - Throws RangeError when responseInit's status is 100"
  "/fetch/api/response/response-error.any.html - Throws RangeError when responseInit's status is 199"      
  "/fetch/api/response/response-error.any.worker.html - Throws RangeError when responseInit's status is 100"
  "/fetch/api/response/response-error.any.worker.html - Throws RangeError when responseInit's status is 199"

If we cared for marketing reasons to pass as much WPT tests as possible, then we could just allow status code 101 or 101-198.

I think there's also a better argument to be made for allowing only 101:

• status codes 100/102/103 are useless in our current model, because these status codes indicate that the server is going to send another response in addition to the 1xx response, but in our API there is no support for sending multiple Responses for a single Request.
• status codes 104-199 don't exist

[bartlomieju]

Fails the following WPT tests:

  "/fetch/api/response/response-error.any.html - Throws RangeError when responseInit's status is 100"
  "/fetch/api/response/response-error.any.html - Throws RangeError when responseInit's status is 199"      
  "/fetch/api/response/response-error.any.worker.html - Throws RangeError when responseInit's status is 100"
  "/fetch/api/response/response-error.any.worker.html - Throws RangeError when responseInit's status is 199"

If we cared for marketing reasons to pass as much WPT tests as possible, then we could just allow status code 101 or 101-198.

I think there's also a better argument to be made for allowing only 101:

• status codes 100/102/103 are useless in our current model, because these status codes indicate that the server is going to send another response in addition to the 1xx response, but in our API there is no support for sending multiple Responses for a single Request.
• status codes 104-199 don't exist

Good point, I think allowing only 101 is a good compromise, but we should update info in MDN compat table too (CC @lucacasonato )

[lucacasonato]

I need to review the implications of this in regards to spec.

[bartlomieju]

This PR allows to ship Deno.upgradeHttp #13618