Geo Replicable - Properly handle disabled verification

What does this MR do and why?

Closes #387069 (closed)

This change exposes the verification_enabled? key to the Geo Replicables Frontend. This allows us to handle the GraphQL query correctly and avoid the need for "dummy" methods to fake their existence when the request is sent. See #385753 (closed) for more info about the error this was causing.

Screenshots or screen recordings

	Before	After
Verification Disabled (the bug)
Verification Enabled

How to set up and validate locally

1. Fetch and checkout this branch
2. Setup Geo (How to setup Geo)
3. In the terminal, go to your Secondary GDK /gitlab directory
4. Access the Rails Console (rails c)
5. Seed a few Container Repositories into Geo (Geo::ContainerRepositoryRegistry.create(container_repository_id: 1, state: "pending")
   • Simply change container_repository_id to a new number for each record you create
6. Access your Primary GDK UI
7. Navigate to Geo Dashboard (/admin/geo/sites)
8. Scroll down to your Secondary Site and click Container Repositories link in the Replication Details section
9. This should navigate you to your Secondary GDK and show a list of the Container Repository Records you created in step 5
10. Ensure NO FLASH ERRORS appear
11. Ensure on each record it says Last verified Not applicable.

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