Successive GH Actions

[alexchristy]

Currently, when we make a PR it runs all the configured GitHub Actions at once in parallel. This helps save time, but often times the first time a PR is made, there are a few linting fixes that need to made, etc. This leads to lots of commits and wasted runner minutes as the unit and integration tests run each time.

I am proposing structuring the tests in the following way:

1. Linting, Type checking, PR label check, etc.
2. Unit tests
3. Integration tests (includes deployed infra tests)

Each step acts as a quality gate for the next set of tests. This will help reduce the number of minutes consumed.

[Adamkadaban]

Great idea. I'm definitely at fault for a lot of wasted minuted lol

[alexchristy]

Fixed in: #114

[alexchristy]

Decided to only make unit tests and integration tests be the quality gate for deployment tests. This will prevent running ~10 minutes of tests deploying infrastructure if the API isn't passing tests.

The linting and PR checks are relatively quick and not worth making sequential as it would just slow down development.