Confusing docker-compose and container Naming Conventions

[jnovack]

Describe the bug
It's super confusing calling the "frontend" container client, and the "backend" container server, when both need to be servers, and neither are clients.

To Reproduce
Steps to reproduce the behavior:

1. Open docker-compose.yml
2. See error

Expected behavior

1. Rename the React front-end client container to something more appropriately descriptive (e.g. frontend)
2. Rename the backend API server container to something more appropriately descriptive (e.g. backend).
3. Rename the bluewaveuptime/uptime_client container to something more appropriately descriptive (e.g. bluewaveuptime/uptime_frontend)
4. Rename the bluewaveuptime/uptime_server container to something more appropriately descriptive (e.g. bluewaveuptime/uptime_backend)

Additional context

• Custom Domain #2110
• Docs and docker-compose for different use cases #2096
• Your Github issue labels are called frontend and backend.