Geo Replicable - Rename Nodes to Sites

What does this MR do and why?

This change is MR 4 of 5 for #393925 (closed)

Geo has rebranded the term Nodes => Sites. We have taken the Facade-first approach to rename only customer facing content while leaving all the technical content like file names, method names, variable names.

Now that the rebrand is mature and we are sure the term Sites is here to stay we are aiming to complete the rename for the technical side of things too.

Focus of this MR

This MR is focused on renaming the FE code that is inside of the geo_replicable scope. This includes all file names, the folder itself, and all component internals.

Screenshots or screen recordings

No change or console errors

Geo Replicable List View

Find in files results

geo_replicable/	spec/geo_replicable/

notes about find results:

1. in geo_replicable/
   • index.js => Multi Version Support, will be removed in #396730 (closed)
   • utils.js => node_proxy renamed to sites_proxy in #396741
   • replicable_type_query_builder.js => Query.geoNode renamed to Query.geoSite in #396739
   • actions.js => Query.geoNode renamed to Query.geoSite in #396739
2. in spec/geo_replicable/
   • mock_data.js => Query.geoNode renamed to Query.geoSite in #396739
   • utils_spec.js => node_proxy renamed to sites_proxy in #396741
   • actions_spec.js => Query.geoNode renamed to Query.geoSite in #396739

How to set up and validate locally

1. Fetch and checkout this branch
2. Setup Geo (How to setup Geo)
3. Access your Secondary GDK UI
4. Navigate to Geo Dashboard (/admin/geo/sites)
5. Scroll down to the Secondary Site
6. Click one of the links in the Replication Details section (ie. Package Files)
7. Ensure the list and any pagination works with no console errors

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.