Implement client side caching for Bodies

Currently the app makes a fresh API call every time a Club or Body profile is opened, even if the data hasn't changed. Since Club and Body profile data (description, logo, members, social links) changes very infrequently, this is unnecessary network usage. The profile should load instantly from cache and silently refresh in the background

**Affected screens:**

- Body profiles
- Explore section - the list of bodies under Tech, Cult, Sports etc should also load from cache

**Expected behavior:**

- On opening a Club/Body profile, cached data is shown immediately
- A background API call is made silently to fetch latest data in both cases
- If new data is available, the UI updates in place (stale-while-revalidate pattern)
- Pull to refresh always bypasses cache and fetches fresh data

Start by locating the Club and Body profile data-fetching paths and the Explore section's list of bodies, then inspect how these screens currently load API data. Done means cached data appears immediately, refresh happens silently in the background, updates appear in place, and pull-to-refresh bypasses the cache.

Written by the indexing model from the issue text.