Fix79: no monitoring caused tests supposed to fail to succeed instead

[lhpt2]

Description

There was a bug that resulted in some tests not failing when the cmd flag --no-monitor is set. Raising a BaseException in the corresponding code that runs when monitoring is disabled (line 210) solves the issue.

Fixes #79

pytest-monitor.py:205 raise e instead of return e

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have made corresponding changes to the documentation
• My changes generate no new warnings
  - [ ] I have added tests that prove my fix is effective or that my feature works
  - [] New and existing unit tests pass locally with my changes (not just the CI)
  - [ ] Any dependent changes have been merged and published in downstream modules
• I have provided a link to the issue this PR adresses in the Description section above (If there is none yet,
  create one !)
• I have updated the changelog
• I have labeled my PR using appropriate tags (in particular using status labels like Status: Code Review Needed, Business: Test Needed or Status: In Progress if you are still working on the PR)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[lhpt2]

Ran into some issues and decided to open a new PR (#81)