chore: initialize pytest and create workflow

[BallardRobinett]

Issue: https://github.com/orgs/bcgov/projects/123/views/2?pane=issue&itemId=49861478

Initializing pytest with a sample test, creating the workflow, and updating the readme with instructions.

To test manually:

In the terminal navigate to the /server/ directory
Do the command pytest
You should get a message like "[100%] 1 passed in 0.00s"

To test the workflow, it should appear as one of the tests that is automatically run when this PR is created.

[pbastia]

Nice work! We just need to make sure we run pytest in the proper virtual environment, with our poetry setup

[pbastia]

we can remove your branch now

Suggested change

	branches: [main, develop, 73-initialize-pytest]
	pull_request:
	branches: [main, develop, 73-initialize-pytest]
	branches: [main, develop]
	pull_request:
	branches: [main, develop]

Since we have the pull_request here, you don't need to explicitely have your branch name in here, you can just open a Draft PR in github and it'll run the actions for you

[BallardRobinett]

whoops, I keep forgetting this. Thanks Pierre!

[pbastia]

I don't think pytest should be added as a dependency for the whole app (we use this top-level requirements file for pre-commit).
pytest is already installed as a dev dependency in /server/pyproject.toml

[pbastia]

This will install the top-level python dependencies, which are separate from our poetry venv and Django app.

You can look at the registration action that runs poetry pytest in the /server/ folder:

https://github.com/bcgov/cas-registration/blob/16db8cf02c7cf429c2da23fe7772c227d595b05b/.github/workflows/test.yaml#L225

[pbastia]

This job could greately benefit from caching to avoid reinstalling all dependencies every run