Add a recipe about custom factories for specific needs

Precondition: [docs](https://farfetched.pages.dev/recipes/cache.html#hashing-algorithm)
```
So, the key is a hash of the following data:
- SID of the Query
- params of the particular call of the Query
- current values of all external Stores that affect Query
To get short and unique key, we stringify all data, concatenate it and then hash it with SHA-1.
```

Usually we have a lots of queries which is tied to user session. Common usecases:
- active user organization (in cases where app have two-layer auth).
- current role(permissions) of user (backend can in runtime change it)

But there is no api to provide this knowledge for cache (it usually does not passed in params but backend takes it from session tokens)