Migrate collection elements store to Pinia

[davelopez]

Migrates the collectionElementsStore from Vuex to Pinia and modernizes the CollectionPanel component. Also tightens the type annotations in the related API schema models.

TODO

• Enhance some type annotations in the API
• Use Fetcher to request data
• Create a new Pinia store for collection elements
• Cleanup unused code

BONUS

• Migrate CollectionPanel component to composition API + Typescript
• Explore ways to improve the scroll experience for large collections (I'll follow with the changes after experimenting in a different PR)

How to test the changes?

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.

License

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

[davelopez]

I think this is ready for review. I will continue with the collection scrolling improvements in a different PR.

[davelopez]

Hmm, test failures seem related... Investigating... 🔎

[davelopez]

I think I found out what was causing these Framework test failures after fixing the response type annotation for GET api/dataset_collections/{id} and making it more accurate with HDCADetailed.

The issue was that the validation for elements_datatypes: Set[str] was failing because those tests were returning [None] instead of an empty list or a proper extension name. The quick fix is in 4b2e2be, but I wanted to make sure this was not hiding another problem and it is the correct fix.

[davelopez]

I'm not sure what is going on with test_history_multi_view.py::TestHistoryMultiView::test_list_list_display I would say it is related to these changes, but It consistently passes for me locally.

Can someone try to run it and check?

[guerler]

Test passes consistently locally. Seems to be unrelated to this PR. PR looks good to me, works fine, is definitely a step into the right direction. Thank you @davelopez.

[davelopez]

Thank you @guerler for the quick review!

I'm still a little worried that the selenium test test_history_multi_view.py::TestHistoryMultiView::test_list_list_display might be now flaky as it also fails in the follow-up PR #16738 based on this one.