Feat/adding unittests for k8s prereq module

[boekhorstb1]

• added unittests: note that these only run with pytest currently. Try: .venv/bin/python -m pytest tests/modules/test_k8s_prerequisites_check.py
• when running with unittest there are various import errors. Try: /app/rookify/.venv/bin/python -m unittest /app/rookify/src/tests/modules/test_k8s_prerequisites_check.py, also note that these import errors do not occure when testing ExampleHandler module, yet import is done in the same way. Try: /app/rookify/.venv/bin/python -m unittest /app/rookify/src/tests/modules/test_example.py
• because the ModuleHandler loads all the module, I found that I had to mock the class TestK8sPrerequisitesCheckHandler itself, thereby keping the code for preflight method the same... maybe you know another way to mock the ModuleHandler before it gets loaded?

[NotTheEvilOne]

pytest is required for unit testing. pyproject.toml contains configuration to make it work as expected which unittest to not support (even by command line argument). Later is at least true for 3.12.3 of Python at the time of writing.

load_modules() is not mockable at the moment as it scans through the rookify.modules directory to identify modules to be loaded.

[boekhorstb1]

forgot to merge this, now have to repair conflicts :)

[boekhorstb1]

ok repaired it and added another small unittest

[boekhorstb1]

Ok I noted an issue: there seems to be some discrepancy between the local pre-comit and the pre-commit run in github actions. I now ran git commit --no-verify to avoid the local pre-commit throwing an error: github actions seems to run through everything fine though

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[NotTheEvilOne]

LGTM