[keyserver][lib] replace neynar client cache with redis cache
Summary:
we're using redis because we have multiple keyserver nodes that will need access to this data in order to minimize the number of neynar client calls
instead of caching led channels by the lead user, we cache all channels we get from the fetchFollowed neynar client method by channel ID. we do this in the background since we don't need to block on this operation.
Depends on D13636
Test Plan:
tested this in a few different ways:
- commented out the background operation that sets data in the cache. registered a user with j4ck.eth's fid and confirmed that user was made lead of bromero community, which they lead on farcaster
- uncommented the background operation. deleted and registered j4ck.eth again and confirmed that the information was fetched from the cache using redis-cli monitor. once again, user was made lead of bromero community
Reviewers: ashoat
Reviewed By: ashoat
Subscribers: tomek
Differential Revision: https://phab.comm.dev/D13637