AddThread without creating a log about go-threads

[sanderpick]

Hi Roman! Great idea. I believe we used to lazy-create logs in the way you describe, but that behavior was changed for some reason. Sleuthing threw the commit history, I honestly can't remember why. I have a feeling it was related to using the a thread node from the JS client. Does this ring any bells @carsonfarmer ?

tl;dr, sounds like a good idea to add that back now.

[carsonfarmer]

Hmmm, I think it was something to do with our multi-tenant setup, and "joining" threads that were already locally available on the remote node? Either way, it seems like the constraint could be relaxed? But we will defs have to test this before deploying anything. I'll have to dig in to be sure. It might also have something to do with differentiating between a thread "owner" (the node owns the thread and has full private key support) vs thread "users" (only have a log, but the private key isn't available locally/on the node).