Registry dataset list on Network page

[ramfox]

closes #425 closes #421

• [x] sometimes there is weird behavior on the dataset history page when the dataset was not pulled from the network. Going to remove the history tab when the dataset was pulled from the registry
• [x] Create function in qri that gets registry via endpoint
• [x] Create actions in frontend that gets registry dataset:
• [x] loadRegistryDatasetByName
• [x] loadRegistryDatasetByPath
• [x] make fromRegistry adjustments in DatasetHeader

---

edit: after talking with Brendan, going to remove the new registry section of entities, and have all the datasets live in one place. So much nicer.

Here are the other things that this pr covers:

• [x] check for profile photo bug

  Walking back some network additions:

• [x] remove registry schemas

• [x] remove registry section from entities

• [x] update selectors to pull from the correct section

• [x] double check actions for any needed changes

• [x] remove /network/ route

• [x] remove RegistryDatasetContainer & any references

• [x] remove anything that links to /network/ route

• [x] add isRegistryDataset(path) selector

  • should find if it is in the list of registry ids
  • if not, return false
  • if yes iterate through other dataset sections to see if it is also in there
  • if yes, return false
  • otherwise return true
  • [x] add isLocalDataset(path) selector
    • isLocalDataset should check the local pagination ids and if the hash exists in this location, then it is local

• [x] isLocalDataset should check the local pagination ids and if the hash exists in this location, then it is local

  • if there is no hash => we need to check via name => for each hash, check select the dataset and check if the name and dataset name match. Return true if so.

  • [x] add isLocal var to dataset and dataset container

  • [x] add fromRegistry var to dataset and dataset container

  • [x] add datasetLinks function that determines the links to pass to the navLinks page (using datasetRef, fromRegistry, and isLocal)

    • overview = always
    • body = filter out if !fromRegistry
    • meta => filter out if section not present
    • structure => filter out if section not present
    • transform => filter out if section not present or scriptPath not present in section
    • viz => filter out if section not present or scriptPath not present
    • history => filter out if !fromRegistry

  • [x] add buttonFunctions function that determines with functions to pass to the buttonGroup (using isLocal, fromRegistry, isPublished, and isLatestDataset)

    • edit => isLatestDataset && !fromRegistry
    • add => !isLocal
    • delete => isLocal && isLatestDataset
    • publish => isLocal && inMyNameSpace && !isPublished
    • export => isLocal
    • rename => isLocal && isLatestDataset

[ramfox]

I feel good about the pr in terms of the issues that is addresses. I've been dogfooding and seeing other bugs/issues, but out of the scope of what I was initially trying to address.

I say we merge and I'll start new prs for bugs that arise, especially since it will feel like forward momentum.

[b5]

perf. Let's do it!