Geo Primary Verification API: Pluralize routing to data management

Chloe Fonsrequested to merge
582209-data-management-migrate-to-plural-routes into master

What does this MR do and why?

This MR ensures paths to the new data management API, both on the Rails and REST API side allow pluralized model names. Example: navigating to the first project record should be done through admin/data_management/projects/1.

References

How to set up and validate locally

  1. Enable the feature flag in Rails console Feature.enable(:geo_primary_verification_view);
  2. Test the new API endpoint as an admin user:
# Replace YOUR_ADMIN_TOKEN with an actual admin personal access token
curl -H "Authorization: Bearer YOUR_ADMIN_TOKEN" \
     "http://localhost:3000/api/v4/admin/data_management/lfs_objects"

Make sure this returns a 200 with LFS Object records 😊

  1. Test with different model names:
curl -H "Authorization: Bearer YOUR_ADMIN_TOKEN" \
     "http://localhost:3000/api/v4/admin/data_management/snippet_repositories/1"

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.

Merge request reports