- Add “make test” command to lint, test and report coverage
- Add pytest runner 
  - It automatically set up to use the correct Django settings module
  - Runs tests on all the available CPU, I was able to run all the test in total=~30sec using “make test” command.
  - It provides a cleaner error report, compared to DjangoTestRunner
- Coverage
  - Displayed the report on the terminal after the test finish
  - Disable reporting of coverage for test and migration files
  - Enable coverage reporting for the template files
  - “make test” generates HTML reports to quickly check the coverage of each file

This avoids the need to collect static files as part of the testing process
locally and in CI.

However - recommend updating CI to run collect static with the production
settings to ensure that all static files are present

* Make the Projects Enabled consistent between local and remote testing

* Test that if projects are disabled we can still determine applications

* Add feature flag to Project creation
* Show project related UI elements when Projects are enabled
* Enable Project URLs based on feature flag
* Enable projects for testing