Change InvocationsList into a grid using GridList

[ahmedhamidawan]

This removes the InvocationsList component and instead uses the GridList. To make this possible, a few changes were made to the Grid components (such as more field types, non-filterable grid, expandable rows etc.).

The invocations list now appears uniform with the other grids due to this change:

Before	After

One tricky thing here is that; to make expandable rows possible, I had to change the table in GridList from:

<table>
    <thead>... </thead>
    <tr for-each gridRow> ... row cells ... </tr>
</table>

to:

<table>
    <thead>... </thead>
    <tbody for-each gridRow>
        <tr> ... row cells ... </tr>
        <tr v-if=expanded> ... expanded data ... </tr>
    </tbody>
</table>

One alternative is that, we remove the expandable rows functionality (which allows you to see multiple invocations in one table) and instead rely on the invocations panel (screencast below; done in a separate PR) to quick-switch between invocations?

This also adds a Import Invocation button at the top right, which fixes part of #18047

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.

[ahmedhamidawan]

https://github.com/ahmedhamidawan/galaxy/tree/invocations_panel

In this ^ branch, I have added an Invocations Panel for the invocations activity:

invocations_activity_panel_second.mp4

Commit: 984341a

[ahmedhamidawan]

The python linting failures are for ./lib/galaxy/model/scripts/history_table_pruner.py and they seem unrelated to this PR

[nsoranzo]

The python linting failures are for ./lib/galaxy/model/scripts/history_table_pruner.py and they seem unrelated to this PR

Yep, they are solved on dev, you can rebase to get rid of them.