Expose pin queue to framework

[sanderpick]

The current logic around what to send P2P and what to offload to the native background uploader queue is feeling unwieldy. It's going to get even more so.

Proposal: On mobile, instead of adding to the P2P queue, the framework simply adds cafe requests to the native upload queue.

[sanderpick]

This may actually be required to get back to a full working state. Feeling skeptical of relying on the P2P queue for even tiny messages, just because you really want to say, type a message and close the phone... even with a poor connection. We're really setup for total offline first... just need a way to add all kind of little tiny messages (blocks, file indexes, dag node indexes) to the native queue... CLI can stay the same, but really not making sense on mobile.

[sanderpick]

I can wrap the other cafe and thread messages requests with HTTP pretty fast (a day). That would mean we could still, for example, try to send direct P2P, but fall back to an OS specific cafe and thread queue (p2p w/ CLI, background service w/ mobile)

[asutula]

You still feeling like this is a thing to do @sanderpick?