Make tests run against local code, fix syntax warning breaking coverage, and add code coverage generation to github actions

[scott-carroll-verses-ai]

• Update tests so they test against local code rather than the installed module
• Update syntax so the warning around ellipsis use doesn't break coverage generation
• Update github actions to produce a coverage report and attach it to the run

See:

• example run: https://github.com/scott-carroll-verses-ai/pymdp/actions/runs/9488505015
• example coverage artifact: https://github.com/scott-carroll-verses-ai/pymdp/actions/runs/9488505015/artifacts/1595277305

Related to issue #142

[tverbele]

@scott-carroll-verses-ai why should we hack the sys.path for local test execution as opposed to installing the library locally using pip install -e . and then running pytest?

[scott-carroll-verses-ai]

@scott-carroll-verses-ai why should we hack the sys.path for local test execution as opposed to installing the library locally using pip install -e . and then running pytest?

Good question @tverbele . The idea is that you test the code before you install it. Can help with issues during dev re: e.g. needing to wipe out cache and change versions of the lib as you work on the "next" version. i.e. to avoid installing a hacky implementation before testing. YMMV 🤷‍♀️

Happy to chat more but my feelings won't be hurt if you decide to not test that way.