Handle response too large when deployed to Cloud Run

[MrOrz]

When serving 5min video on cloud run, we may encounter this:

Followed by a server restart.

It is possible that we are hitting the 32MB limit in https://cloud.google.com/run/quotas

Using chunked encoding may solve the issue - simonw/datasette#749 When chunked encoding is used, Content-length header is omitted. However, rumors-api requires content-length to do proper processing, thus it cannot be used.

We may need to try setting up http2 connections instead; which may also involve changing to a HTTP client supporting HTTP/2 (or built-in fetch) on rumors-api.