Knowledge entry explaining how to run django tests in Github Actions

[ctmartinez1992]

I wasn't sure where to place this information. I placed it in the testing section, but it seems like it could make sense in the stack and tools section as well.

I made a new page just for this. Right now it only explains how to run Django tests in Github Actions. It makes a lot of assumptions like using poetry and Postgres, but I think that's ok because people can easily infer what may be necessary just by having an example.

I made no mention to the caching possibilities of Github Actions as it can create confusion.

[ctmartinez1992]

I added a github action to run the tests and only deploy if those tests run successfully. Also, the test job always runs on each push, but the deploy job only runs if it's the master branch that received the push.

There's a small issue though: the test job took almost 18 minutes to run and most of its time was spent in the install poetry dependencies step. Is there any reason for this to take so long? I also noticed that when I installed the dependencies locally, it also took a very long time to complete. @JdFSilva@kenvontucky