Enhancement: Make it easier to find input datasets/source histories from workflow created histories

Detailed, but not copying over datasets when a workflow is run changes usage. And other usage improvements could be bundled in, even if they have been possible before (some are probably existing ideas, GH or not).

**Use case:**

Workflow is executed and results sent to a new history. There is an unexpected result or error with a tool that used an initial input (located a different history now) or the problem traces back to an initial input. Or, you just want to rerun quickly without going to saved histories and doing a search, assuming you remember the source history name or know how to find it.

In short, getting back to the inputs or source history is complicated ...

1. The name of the initial history is not easily found and there is no way to navigate back to it or to the initial dataset(s) **directly** (to review, modify, rerun, etc). You need to already know or look up the names and search for them.
1. The history name may not always be correct if the name has ever been changed, including if it was imported and renamed. The original history name is permanent (even more so than it is for share links).
1. The dataset name is hyperlinked on the "view details" i-icon info page, but it points to the info page for the dataset, not the dataset itself.
1. The source history name not hyperlinked on the on the "view details" i-icon info page under the "Inheritance Chain" section. And it might not be correct for the reason in 2 above.

**Few ideas:**

1. Include the input datasets source history as a hyperlink (plain text or actual link) somewhere very obvious in the default view of the workflow created history.
* "Annotation" is one location (would just be plain text).
* Or maybe a hyperlink could be added for this class of history near the top of the panel, under the history name, the way dataset views are hyperlinked (active/deleted/hidden)?
* Also source history hyperlink in the info page (easiest option short term).

2. Add an input dataset's direct link on the "view details" i-icon info page. Could take user to **User > Saved Datasets** page, with a filter for just that input.
* ^^ could be annoying if you want to get access to all of the inputs in one click, unless that is considered when the link is constructed/organized on the form.
* If could get all, this would be a very quick way to subset and copy over just the input datasets into a new history. Maybe you want to purge the entire original source history that contains other analysis without individual clicks (even in batch mode this can be tedious).
* **Or maybe you want to add tags to these datasets (without manual individual searches), because the results were good** (or for any reason)

**Bonus:**

Note somewhere, ideally with a direct hyperlink, the workflow (or workflows) that were used to create data within _any_ history. Could be a multiple listing. And could be later used as a view option when history structures are graphed.
1. However, if individual datasets (not just a history in general) could map back to a workflow and possibly the step within that workflow, it would close a reproducibility loop.
1. Why? The user gains not just info about that individual tool run (existing) BUT contextual information about how that tool was used in a workflow. Adds value to using a workflow (data and job/tool relationships are captured).
1. Is different that just viewing the history structure stand-alone (for when that view is developed further).

Please come up with better ideas. It would be good to get back to the initial inputs easier than it is now.

No files, tests, or entry points are named. Start by examining the workflow-created history default view and its dataset details/info page, then trace how source histories and input datasets are represented. Done would require an agreed, testable navigation design covering the requested source-history, input-dataset, and workflow links.

Written by the indexing model from the issue text.