Ill-defined behavior of Import history from archive

[wm75]

Describe the bug
When you select an archive that is not exactly an archived history under Import history from archive, then there is no strict checking but the import may fail with various messages, or in the succeed with side-effects.

Galaxy Version and/or server at which you observed the bug
tested on usegalaxy.eu

To Reproduce

• If you import a Workflow Run RO-Crate (exported from the workflow invocations page) as a history, you will get a WF added to your WFs, a WF invocation added to your invocations, and datasets added to your current history, but the UI will tell you that it just imported a history.
• If you import a WF invocation exported in "Galaxy native format" (essentially, like a RO-Crate but without datasets), you will also get a WF and an invocation added, but only the last changed date of your current history updated

Expected behavior
While it's super-nice that you can import workflow invocations just like that, it would be better if the History import only accepted history archives and the WF invocations import was moved to separate functionality.
It would also be good if the WF invocations import would (just like the workflow run dialog) ask you if you want to import the invocation datasets into your current history or into a new one.

Both importers should check their inputs and refuse to work with unexpected formats.

[hexylena]

In theory I like the behaviour of "import in one place and get notified" xref #10695, if only notifications were generated for the user of "hey we also imported a history" and "hey we also imported an invocation" and "hey we also found datasets".

[ahmedhamidawan]

Imported invocations can also mess up the step order as can be seen here:

The imported invocation (on top) has the final step of the workflow as the first step instead

[mvdbeek]

That seems like a different issue, can you post an example workflow as a separate issue ?