Feature request: Input data, workflow, and answer key histories in tutorial metadata

Y'all have done such AMAZING WORK figuring out Workflow testing

Rationale: Lots of times data upload/import is the painstaking bit in a live tutorial. Zenodo can be really slow. Having an 'Input history' has been incredibly useful as they import these in seconds, BUT this exists only on one server (the one I made it on, often usegalaxy.eu) and I have (multiple times) accidentally analysed stuff on this history when doing my own work, and then had to go back and delete everything.

And/or there are IT issues or the server is slow etc. etc., and having an "Answer Key history" they can access to start partially from (if things go terribly wrong early on) or at least see how someone analysed the data is super useful. This has saved me numerous times.

SO, can we combine these needs with the Workflow testing?

If we have to include 'input datasets' from the tutorial, and the workflow has to run and successfully create the 'output' dataset, would it be possible to have this somehow then saved as a 'click-to-import' history (just like the amazing click-to-run/import workflows) that bypasses the server differences, AND means nobody has to save the input & answer key histories in their Galaxy space.

Then these could be flagged in tutorial metadata at the top (for example, INPUT HISTORY:  fa-flask | ANSWER KEY HISTORY: fa-key] and pointed to with some FAQ sections on both data import and also troubleshooting.