Refactor Soft Delete Specs

Just for more discussion

This one was much harder. There's a few inline comments I want to make for discussion, but I'd also like input on what's left in https://github.com/OregonDigital/oregondigital/blob/feature/TrySoftDeleteSpecs/spec/features/soft_delete_spec.rb , which is primarily "display things that are queried". Any thoughts on how to pull that out? Or is this just the only way to avoid mucking about in Blacklight stuff?
> I'd use a double instead of stubs and just watch tests fail until I implement enough stubs.

This is a good point. Maybe the act of using a generic asset rather than a double with the relevant interface is too much even. I know I'd get swamped into stub-land, but that'd be a good sign that there's an architecture problem.