[Feature Request] suite_setup and suite_teardown

[beccasaurus]

Some tests require multiple resources to exist.

Take the case of: creating a Job (job_service.CreateJob)

To be able to create a Job, you need:

1. A "tenant"
2. A "company"

So this means that, if I have 10 Job tests and I setup/teardown these sources for each test case, the suite makes 20x create API requests and 20x delete API requests (40x requests)

If we had suite_setup (or something similarly named) which ran before the whole suite, we could reduce this to 2x create calls and 2x delete calls (4x API calls = 1 order of magnitude fewer)

test:
  suites:
  - name: Manage Cars

     suiteSetup:
     - # create a dealership which is shared by all test cases
     - # uuid: dealership_id
     - # call: something to create dealership resource

     suiteTeardown:
     - # delete the dealership

     cases:
     - name: Create Car
        spec:
        - call:
             sample: create_car
             params:
               dealership: dealership_id
               make: Chevrolet
               model: Colorado