Support response caching of API responses

[jezzsantos]

Response caching, in web APIs and web applications is a complex topic, and can refer to many related mechanisms, lets be clear on the main mechanisms involved:

1. HTTP response headers, defined by the server on responses. (This is not actually caching, rather an instruction for a client)
2. Output caches on the server controlled by the server, used to serve responses (usually per unique request, varying by all parameters, path and query)
3. HTTP client caching, where clients/intermediaries act on the declared HTTP response headers from server (usually performed by intermediary infrastructure)
4. Client application caching, where clients (like JavaScript frameworks) maintain their own caches in the browser, to prevent themselves reissuing requests to servers.

These are the most common types, there might be others.

All these mechanisms are in play at all times, and are all orthogonal and mutually exclusive to each other.

Which means we need to take great care to manage them or coordinate them with other mechanisms that may also be in play.

Caching is also (one of those things) that is optional until it is needed, and then great care should be applied since cache invalidation is a huge problem to deal with, particularly with usability when it comes to volatile data.

[jezzsantos]

With 0cb6719 We now have a basic implementation of client application caching for easy declaration on each client API request.
The cache (TanStack Query) manages a straightforward TTL for all cached items, using a simple hierarchical cache-key mechanism.

For example when requesting a specific Organization, using the respective QueryAction, we use the cache-key: ["orgs","org_1234567890"] to fetch it, with a global TTL of 60secs.

After 60secs this cached value expires (goes stale) and eventually is destroyed garbage collected.

While it is cached, if we update this specific org using a CommandAction, we can specify the same cache-key value, to signal to invalidate that specific cached data.

We can also force all organizations in the cache by invalidating this cached data-key: ["orgs"].
(As you see in the LoginCredentialsAction after successfully signing in a new user.

[jezzsantos]

Closed by ed3a162