Yarn (all) tests should start/tear-down their own env and be idempotent #101
Description
Currently, some project tests expect the network to be running externally before they are started, others don't have that requirement and start their own network programatically on beforeAll.
These two workflows conflict if they are ran together - no network cleanup, port conflict.
Ideally, we provide env access programmatically, so each test suite can manage their own.
Originally posted by @krebernisak in #93 (comment)