Geo Replicables - Use backend as SSoT for Replicator Data

What does this MR do and why?

Relates to #219942 (closed)

We currently utilize a getter to parse out the human-readable names for replicables in the Geo Replicables List. However, everywhere else in the application we utilize the backend properties that already generate these values for us. This change removes the custom getter and instead utilizes the backend as the SSoT to align with the rest of Geo.

Screenshots or screen recordings

The main UI change is via Capitalization. In this context the Registry types are proper nouns and I am a fan of capitalizing them as they are often capitalized in other parts of the application.

Before	After
Before	After

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

1. Access your primary GDK Geo Page (127.0.0.1:3000/admin/geo)
2. Scroll down to the very bottom Replication details section and ensure all the names are readable.
3. Click one of the blue links (ex: Project Repositories)
4. Ensure all the tabs, list items, and filters are readable
5. Click the Resync all or Reverify all actions, ensure the modal that appears has the human readable name for the tab you are on.

Related to #219942 (closed)