Rename the "ingestion server" to "data refresh"

[AetherUnbound]

trafficstars

Problem

We are using the legacy name "ingestion server" for a server that is performing our data refreshes (see https://github.com/WordPress/openverse/discussions/107).

Description

I would like to propose that we rename the ingestion server and all associated assets (Docker images, private DNS names, references, etc.) to "data refresh" or "data refresh server". This will make it clearer what action the server is performing, particularly since we are still overloading the term "ingestion". Renaming it to data_refresh also helps us remove the redundant _server suffix everywhere.

Alternatives

If anyone is against this change or would like to propose an alternate name, please do so by 2022-03-04.

Additional context

Implementation

• [ ] 🙋 I would be interested in implementing this feature.

[stacimc]

Making a note to update links in the Catalog's dags/data_refresh/dag_factory.py added in https://github.com/WordPress/openverse-catalog/pull/397

[stacimc]

Making a note that we'll need to update the system architecture diagram as well when this is changed.