Edge Caching

## Feature Description
Ability to cache on the edge to reduce origin traffic and increase performance of your APIs

## User value / outcome
Improving on the current V2 caching feature by providing the ability to cache near the client in a content delivery network CDN-like fashion. Achieve even lower global P95 response time while reducing server load as much as 90%.

## Current status (design, alpha, beta etc.)
Hasura V2 Caching feature (using cached directive) on the edge expected by Q3 this year. Discovery in progress for other caching features such as -

- Server Side Caching (including cached List)
- Caching near the data source
- Cache on AuthZ (object ID based caching)
- Caching on external REST API (preventing data leaks becomes an issue if we combine with Cache on AuthZ idea)
- Smart Caching (partial caching - cached subsets)

Please comment on this issue with more information on your use-case or to upvote any of the ideas mentioned above

No files, tests, or implementation entry points are named. Start by reviewing the existing Hasura V2 caching feature and the listed discovery areas, then clarify whether edge/CDN caching is the intended scope and define the caching, authorization, data-source, and REST API boundaries. Done means an agreed design and implementation scope for the selected caching approach.

Written by the indexing model from the issue text.