Adjust package history loading skeleton

What does this MR do and why?

Adjust loading skeleton for package history so that it better matches the actual layout of history items.

Note

The related issue (#363820 (closed)) calls for "using utility classes" for the skeleton loader, but that advice is out of date (it predates the implementation of our tailwind utils). We use direct numerical values to define custom skeleton loader shapes in every use of the GlSkeletonLoader component where custom shapes are used.

References

Screenshots or screen recordings

Before After
gdk.test_3000_flightjs_Flight_-_packages_48 gdk.test_3000_flightjs_Flight_-packages_48__1
Screen_Recording_2025-04-15_at_15.36.18 Screen_Recording_2025-04-15_at_15.35.59

How to set up and validate locally

  1. Check out this branch
  2. Visit a package page in package registry in a project
  3. Apply this patch so that the history will always be in the loading state 20250415-package-history.patch
  4. You will see that the loading state matches the layout of the actual history items

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #363820 (closed)

Merge request reports

Loading