qri get for a dataset ref not in repo returns "logbook: not found" or "reference not found"

[dustmop]

> qri get other_user/data_i_dont_have
logbook: not found

for a new user (I think the root cause here is not being cloud connected, unsure):

> qri get other_user/data_i_dont_have
reference not found

My understanding is that this should instead be resolved by the registry. Don't believe there's any tests for this functionality, so it's easy to end up broken.

[dustmop]

Still getting "logbook: not found" for certain datasets, but not getting "reference not found" anymore.

> qri get xristosk/bot_sentinel_trolls
logbook: not found

> qri get mfdz/stuttgart_gelbekarten
pulling mfdz/stuttgart_gelbekarten from http://registry.qri.cloud ...

[dustmop]

Figured out part of this problem, qri pull used to not add logbook data to your own repo, so when we try to locally resolve such a reference, there's no initID. Running qri pull again will fix this case. However, we have at least a few users that have divergent profileIDs, because cloud does not check for bad push data. When those datasets exist in a repo, the old fix to merge logbook by profileID fails because the user has two different profileIDs, leading to the same situation of a reference existing in your repo, but not being usable.