[ResponseCache] Should response be cached only if all types have opt-in

With the current implementation, a response is cached based on if at least one type or field is cachable in the response.

Apollo's response cache plugin is doing things the other way around: the response is cached only if **every** fields and types have a TTL greater than 0 (which is the default TTL for every composite types or fields).

The Apollo's approach makes the caching more predictable, since an entity can't be cached just because some other entity in the response is marked as cachable.

Should we do the same thing ?

## Additional context

Here are more details on their philosophy on this: https://www.apollographql.com/docs/apollo-server/performance/caching#default-maxage