[BlueskyBridge] prevent 408 request timeout by implementing cache

[mruac]

PR implements a cache on the user handle to DID resolution for up to a week to prevent the resolution being performed each time the feed is generated. Could be permanent, but I don't like it sitting around in the cache permanently. Also added to user profiles (custom name, avatar and description) to the cache for up to the defaulted day.

In the future, I would like the bridge to resolve the user handle to its DID and redirect to itself with the DID as the user_id if a handle is provided (handles can be changed, DIDs cannot), and in turn automatically correct any currently subscribed feed urls that is using the user handle as the user_id parameter. This will require implementing a HTTP 301 redirect. Please see #4663 for a discussion on this.

Also added more semantics.

[github-actions]

Pull request artifacts

Bridge	Context	Status
Bluesky	1 untitled (current)	✔️
Bluesky	1 untitled (pr)	✔️

last change: Wednesday 2025-10-29 21:40:33

[dvikan]

bridges have access to cache like this: $this->cache->get('hello')

i'd prefer we deprecate $this->loadCacheValue (which is simply a convenience wrapper)

[Mynacol]

I rebased this and changed it to use the new cache functions.
LGTM now.