Pytest-cases

- Fixed an issue where a lazy value would not be resolved. This happens when the "auto-simplify fixture" happens in `parametrize`. Fixes [225](https://github.com/smarie/python-pytest-cases/issues/225)

- Fixed most `flake8` errors and updated documentation to use `genbadge`. Fixes [223](https://github.com/smarie/python-pytest-cases/issues/223)

- Fixed `ValueError` when `parametrize` is used to parametrize a class. Also, added a more explicit `TypeError` when `parametrize` is used to parametrize a class and at least a fixture reference is present. Fixed [215](https://github.com/smarie/python-pytest-cases/issues/215).

- The `current_cases` fixture now contains case parameters if any. Fixes [214](https://github.com/smarie/python-pytest-cases/issues/214)

- The `current_cases` fixture entries are now instances of `namedtuple`.

- New `in_cls` argument in `unpack_fixtures` so that it can be used inside classes. Fixes [201](https://github.com/smarie/python-pytest-cases/issues/201)

- Fixed minor issue where empty entries could be present in `currentcases`. Fixes [213](https://github.com/smarie/python-pytest-cases/issues/213)

- Fixed issues where the `currentcases` fixture would not return the correct case function. Fixed [212](https://github.com/smarie/python-pytest-cases/issues/212)

3.5.1 - python 3.10 compatibility + improved error message

- Fixed error message related to misuse of `fixture_ref`. Fixes [209](https://github.com/smarie/python-pytest-cases/issues/209)
- Fixed import error with python 3.10. Fixes [207](https://github.com/smarie/python-pytest-cases/issues/207)

- New: Users can now easily access the current cases for each parametrized argument thanks to the new `current_cases` fixture. A new helper function `get_current_cases` is also provided, for direct access from a hook. `get_current_case_id` becomes deprecated in favour of these two. Fixes [195](https://github.com/smarie/python-pytest-cases/issues/195)

- Bugfix: Fixed issue where the cache of a `lazy_value` used for a tuple of parameters (several `argnames`) was not considering the pytest context and thus was wrongly used across pytest nodes. Fixes [202](https://github.com/smarie/python-pytest-cases/issues/202)

- Improved error message when a fixture parametrized with several argnames as once is not able to unpack the parameter values received (non subscriptable object).

- `parametrize_plus` and `fixture_plus` are now deprecated in favour of `parametrize` and `fixture`, as most users seem to have adopted these names without issues.

- (internal) Replaced the `"used"` parameter with a dedicated singleton `USED`