Storage restore optimization

[mrdotb]

I have an idea to speed up the storage restoration process. Instead of storing the error fingerprint in the thread title, we could create a dedicated thread and use a text message or blob to store a mapping between the fingerprint and thread ID.

Each message can hold up to 2,000 characters, which should provide ample space for storing the mappings. On startup, we can parse these messages and load the mappings directly into our GenServer.