Consider separate EC2 machines for the sync-wrds-location-db and hv-vpp-ti-db-dumps-to-s3 step functions

[shawncrawley]

The sync-wrds-location-db and db-dumps-to-s3 step functions both currently leverage the hv-vpp--rds-bastion EC2 to execute their database code. This makes sense, since the rds-bastion machine is already configured to interact with the DB. These functions should both power off the machine when they are not using it, so as not to incur unneeded costs. Unfortunately, it's very possible (and has already actually occurred) that they are running at the same time, and whichever one finishes first turns off the machine while the other one is still processing, prematurely killing that process.

We either create (a) new, isolated EC2(s) for these separate processes, or come up with some way to check if something else is running before shutting down.