Geo Node Status 2.0 - Replication Counts

What does this MR do?

This MR breaks off from the UI mega MR: !53090 (closed)
Work towards #287978 (closed)

This change replaces the placeholder Replication Counts with the actual component. The logic here intends to aggregate a bunch of data values/counts and create an overarching percentage of success/failure and render it on the screen. Most of the logic is in the getter, which is then used in the computed to group the data into 4 sections:

1. Git (aka Repositories) Sync Status
2. Git (aka Repositories) Verification Status
3. File (aka Blobs) Sync Status
4. File (aka Blobs) Verification Status

This MR still leaves a placeholder in the secondary replication overview for a future MR.

How to test

1. Set up a Geo Primary/Secondary GDK
2. Fetch the current branch
3. Activate the Feature Flag on your Primary GDK (:geo_nodes_beta)
4. Navigate to http://127.0.0.1:3000/admin/geo/nodes_beta
5. View UI

Screenshots (strongly suggested)

	Desktop	Mobile
Before
After

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