run each migration in its own transaction

Running the whole set of migrations in a single transaction (the TypeORM
default) would cause issues with some enums not being committed before
they are used. This wasn't causing issues so far in the CI pipelines
(where the change in this commit is relevant) just because of an
unrelated bug that caused migrations runs to be tried twice (with
nothing being done the second time through the shell command changed in
this commit as the migrations had already run).

api/apps/api/entrypoint.sh

@@ -18,7 +18,7 @@ case "$1" in
     run-migrations-for-e2e-tests)
         echo "(ESC)[44m Running migrations (api db) for e2e Tests in Api (ESC)[0m"
         sleep 15
-        exec yarn api:typeorm migration:run
+        exec yarn api:typeorm migration:run -t each
         ;;
     start)
         echo "Running Start"

api/apps/geoprocessing/entrypoint.sh

@@ -17,7 +17,7 @@ case "$1" in
     run-migrations-for-e2e-tests)
         echo "(ESC)[44m Running migrations (geoprocessing db) for e2e Tests(ESC)[0m"
         sleep 15
-        exec yarn geoprocessing:typeorm migration:run
+        exec yarn geoprocessing:typeorm migration:run -t each
         ;;
     start)
         echo "Running Start"