Fix pin bugs

[mason-fish]

fixes #1166

There were a few inconsistencies in the tree view, and this PR aims to fix them with these changes:

• When clicking on any part of the investigation tree, the value you click on will go to the search bar and any of it's parental lineage will be be used as pins. Previously the underlying query was being used, even if you had only intended to use a fragment of that original query.
• When deleting an entry from the tree, we use the underlying values as well, but now we inform the user about that behavior.
• Replaces our own Tree class with the tree-model package we are using in the query lib reducer.

[jameskerr]

This behavior is much more strait forward now. Thanks for swapping in the tree-model too.

I noticed that we provide an "are you sure" popup now in the tree view, but we don't in the linear view. Was that your intent? I think it might be cumbersome to click through that each time I wanted to delete something from the tree. What do you think about changing the label from "Delete" to "Delete underlying entry"? That might provide enough of a warning to the user without making them click through a popup. It would also match the linear view. What do you think?

[jameskerr]

I think might be simpler as a map function: node.getPath().map(n => n.model.filter)

[jameskerr]

Is this the same as saying node.children?

[mason-fish]

As mentioned offline: no, all() is similar to a descendants() or function which recursively returns all children, grand-children, etc. It just takes a predicate function which I'm not really utilizing any sort of filter here, hence () => true (return all nodes)

[mason-fish]

@jameskerr I agree the dialog was a bit too much, here is the new behavior:

[jameskerr]

Thanks! Looks good