Geo - Provide replicable types list to Frontend

What does this MR do?

Closes #228700 (closed)
Unblocks #228722 (closed)

This change allow the frontend to no longer need to manage a hard-coded list of Replicable Types for the Geo Node Status Bars.

Instead the backend will now manage the list. Currently there are some legacy types that are hard coded until they are eventually added to Geo Self Service.

All the Self Service data types are added automatically via a loop through the available replicable classes. Eventually, once all the legacy types are transferred, we will no longer need to maintain this list as the machine will generate it automatically.

Screenshots

Response in frontend

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team

Closes #228700 (closed)