Increase mypy strictness and fix issues about cyclops HOT 3 CLOSED

@fcogidi, @a-kore I've created PRs #389 and #390 to fix mypy errors for the evaluate and monitor packages respectively. This is not high priority and can be done when you get time, especially i would recommend doing this once the package is refactored and we have the demos using the APIs more mature. But opening it now, so we can slowly fix the type hints and improve the codebase.

from cyclops.

As a possible approach for this, you might consider looking at the PR here. You don't need to worry about most of the files there, but the following are likely relevant:
.pre-commit-config.yaml
run_mypy.sh
mypy.ini
pyproject.toml
I put some comments around these changes in the PR, but the gist is that running mypy . is significantly more strict than running the mypy checks through pre-commit run --all-files because pre-commit is run in an isolated environment, which changes the way types are interpreted etc. So we need to put

entry: ./run_mypy.sh
language: system```

into our pre-commit so that it runs in the system's currently activated env. We also want to manipulate the entry point to run a script so that the mypy.ini settings are explicitly brought into the pre-commit run.

from cyclops.

PR #389 done.

from cyclops.