Improve documentation Response Caching documentation

[EmrysMyrddin]

Response Caching documentation is too light. It only describe the specific differences with the Envelop plugin and links to it for more informations, which is not handy for the reader.

It is even less appropriate now that more and more options slightly differs between Yoga and Envelop plugin.

This issue aims to keep track of the actions to improve this documentation page.

• Copy and adapt the recipe section from the envelop's plugin documentation
• API style documentation, with an entry for each option.
• Migration guides from popular alternative (like Apollo's response cahing)
• Knowledge base about caching.
  • Why is it needed
  • How does it works
  • Which strategy are possible, and when to use them
  • Advices about cache invalidation, how to properly do it, what common edge cases and pitfalls are and how to avoid them.

[AdiRishi]

I'm really curious about this tbh, is it possible to give a brief explanation on the differences between yoga response cache and the envelop plugin?

[EmrysMyrddin]

@AdiRishi The Envelop plugin is the base one, handling cache at a GraphQL level, without any assumption about the transport layer that will be used.

The Yoga plugin rely on the Envelop plugin, notably for the cache write part, but adds support for HTTP specific caching techniques using E-Tags header requests for example.

This allows us to achieve even better performance in yoga by skipping entirely the GraphQL pipeline when possible.