`dekick yarn test` should notify the user that the tests will be run on the local database

[akucintavalent]

My colleague wanted to run tests and he used the command dekick yarn test instead of dekick test. He wasn't aware of the fact that the tests will create new records in his local database. Whereas dekick test creates local database adn later erases it.

[fojuth]

Maybe dekick could set a env variable with the command that was actually ran? We could then choose not to run a particular test because it does something in the DB. Or we could clean up after running this test, if it was running on the local DB. For example, consider this - DEKICK_EXECUTED_COMMAND=dekick yarn test.