Enable type-checking for examples

[thierry-martinez]

This commit adds type annotations in all example modules, and refines the type of PatternSimulator constructor, so that the type parameter for states is automatically inferred from the backend argument.

It enables full type-checking with mypy and pyright while preserving existing functionality across the entire code base. No files are ignored by the typers anymore.

Related issue:
This commit continues the work started in #302, #308, #312, #347, and #414.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.06%. Comparing base (ed6b394) to head (edbcf45).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #430 +/- ##
=======================================
Coverage 88.06% 88.06% =======================================
Files 44 44 Lines 6433 6433 =======================================
Hits 5665 5665 Misses 768 768 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[emlynsg]

Looks good to me. Do we mind that there are still lots of Pyright warnings?

[thierry-martinez]

Actually, they were only three warnings:

• one warning Import "setuptools" could not be resolved from source (reportMissingModuleSource): I believe there is nothing to do about that; we could disable reportMissingModuleSource completely, or make pyright ignore setup.py, but I am not sure what is preferable;
• two warnings reportInvalidTypeVarUse that can be considered as real issues: I turned them into errors in pyproject.toml and fixed them in 77a2858.

There are 395 informations: we can see if there is something we can do with them at some point, but I consider it is out of the scope of this PR!

[matulni]

Thanks for taking the time to do this! Looks good!