+hco #15835 we can keep the toStrict'ed future around...
plenty of downsides though:
- heavy atomic reference field inside of HttpEntity
- for 2 calls to toStrict with different timeouts, the first one wins
- general downsides of using toStrict remain unchanged

upsides:
+ all toStrict callers will eventually get the value, so behaves like
  old spray http