* [FIX-CONFLICT-WITH-RSTEST-V2]: semi-stable version, fix test_context function, remove unnecessary field, remove wrapper function, add ability to work with rstest and same
* [FIX-CONFLICT-WITH-RSTEST-V2]: stable version, fix bugs with AssertUnwindSafe in sync_wrapper_body, remove redundant code, fix two tests, add notes for this tests
* [FIX-CONFLICT-WITH-RSTEST-V2]: stable version, fix context name extraction function, fix readme, fix docs, increase version of crate
---------
Co-authored-by: Vyacheslav Volkov <v.volkov@st-falcon.ru>
By exporting the futures crate through the test_context crate, the code
generated by the macro can rely on `test_context` to access the future
crate. Otherwise, the code generated which requires access to the
"future" crate would end up residing in the code of a user of the
library, giving them `use of undeclared crate or module "future"`
error messages unless they added future as a dependency.
