Constrain memory allocation for stat server task

We need to leave some overhead for any scheduled tasks (esp. materialized view updating), so we must make sure that the task definition applied to the stat server has a memory allocation of 1G. The current process of deploying the stat server (`make start-service` in `deployment`) does not do this and is causing problems.

Start in the deployment directory and inspect the make start-service target and the task definition it applies to the stat server. Confirm how memory is currently assigned, then make the completed deployment reserve 1G for the stat server while leaving overhead for scheduled tasks such as materialized view updates.

Written by the indexing model from the issue text.