Stabilize backend deployment

[blairlyons]

• [ ] https://github.com/simularium/simularium-engine/issues/71
• [ ] https://github.com/simularium/simularium-engine/issues/72
• [ ] https://github.com/simularium/simularium-engine/issues/73
• [ ] https://github.com/simularium/simularium-engine/issues/74
• [ ] https://github.com/simularium/simularium-engine/issues/75
• [ ] https://github.com/simularium/simularium-engine/issues/76
• [ ] https://github.com/simularium/simularium-engine/issues/77
• [ ] https://github.com/simularium/simularium-engine/issues/78
• [ ] https://github.com/simularium/simularium-engine/issues/79

Use case

As a developer, I want to know the backend deployment is stable and be able to easily monitor and troubleshoot when it is not.

Acceptance Criteria

• backend components are up to date
• backend logs are easy to find and interpret
• backend deployment is fully automated
• backend monitoring is either automated or easy for developers to check

[blairlyons]

also account for these issues or verify that they're outdated:

• https://github.com/simularium/simularium-engine/issues/44
• https://github.com/simularium/simularium-engine/issues/43
• https://github.com/simularium/simularium-engine/issues/40
• https://github.com/simularium/simularium-engine/issues/39
• https://github.com/simularium/simularium-engine/issues/38
• https://github.com/simularium/simularium-engine/issues/24