[24.1] Record implicitly converted dataset as input dataset

[mvdbeek]

by fixing the converter's output dataset extension to the requested extension.

We don't need to wait for the galaxy.json collection, we know the exact
target type already. That fixes the retrieval in
get_converted_files_by_type.

I believe this was always the intention and is how it works if the
dataset already exists (i.e. on a re-run), and for all converters that
don't use galaxy.json The converter records the dataset that the user
chose, so there's no gap in the provenance either.

This somewhat addresses
galaxyproject/total-perspective-vortex#141
so you can (reliably) differetiate your rules on the input datatype
and filesize combination.

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.