Data Management: Hide checksum info when disabled

What does this MR do and why?

Closes #587189 (closed)
This change is behind a feature flag :geo_primary_verification_view

The Data Management view is currently tied to Geo but there are scenarios where checksumming can be disabled for a particular model. If this is the case we should hide the actions and checksum information as it will all be nil and the actions will not work.

Screenshots or screen recordings

	Checksum Enabled	Checksum Disabled
List View
Details View

How to set up and validate locally

Setup Geo (optional)

Important: To properly test Geo you will need a separate GDK setup. Setup is straightforward but takes some time. Another option is to validate the code functionally and if needed schedule a call to sync and I can screen share my instance.

1. Ensure no other GDKs are running. gdk stop/gdk kill
2. Open an empty directory and install and run Geo with the one-line command found on the Easy installation instructions
3. Access your primary and secondary Geo instances via 127.0.0.1:3000 and 127.0.0.1:3001.

Testing

Checksum Enabled

1. Enable the feature flag Feature.enable(:geo_primary_verification_view)
2. Access Data Management view (/admin/data_management)
3. Ensure list view shows checksum info
4. Click into a record
5. Ensure details view shows checksum info

Checksum Disabled

1. Enable the feature flag Feature.enable(:geo_primary_verification_view)
2. Mock checksum_enabled as false: https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/helpers/ee/geo_helper.rb#L96
3. Access Data Management view (/admin/data_management)
4. Ensure list view does not show checksum info
5. Click into a record
6. Ensure details view does not show checksum info

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 #587189 (closed)