Uses shared registry-list component to render package other versions

What does this MR do and why?

Refactor packages other versions list to use shared component so that bulk delete can be implemented in the follow-up MR.

Screenshots or screen recordings

No visual changes

How to set up and validate locally

1. Follow instructions to publish new packages
2. Publish more than 20 packages with same name & different versions, as mentioned in https://gitlab.com/gitlab-org/ci-cd/package-stage/package/-/wikis/Packages-Tips-&-Tricks#how-to-create-a-list-of-packages-artificially
   1. rails c - Open the rails console
   2. p = Project.find(1) - Find one of your GDK projects. Project id can be found on the project home page
   3. FactoryBot.create_list(:npm_package, 25, project: p, name: p.name) - Creates 25 npm packages
   4. Add this line if above fails during the creation of the files

       def fixture_file_upload(*args, **kwargs)
         Rack::Test::UploadedFile.new(*args, **kwargs)
       end

3. Visit package registry list page for groups & projects.
4. Visit the package detail page > Other versions tab
5. Should be able to paginate between pages

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #374295 (closed) #361304 (closed)