Allow multiple form and wizard libraries (or, "the future of formik-wizard")

[zaguiini]

Back in 2019, when I first started working on this library, it made sense to base its scope solely on formik and react-albus, which were arguably the best two libraries in their segment and covered most use cases.

Fast forward to 2020, I'm not sure if this statement holds true and people are using different form libraries (like react-final-form) and wizard libraries (using react-step-wizard) as examples.

Limiting this library to formik and react-albus could be a show stopper for people that are not actually using them. Ideally, the library should be adaptable to whatever solution the target developer likes.

I've started implementing something, but due to lack of availability I'm unable to complete this POC/MVP, but here is the repository. There's also an example usage, if you want to check how to use the new project.

I really think this could go forward and, ideally, we could expose a generic adapter for forms and wizard libraries (or components) so it become as flexible as it could be.

Feel free to contribute and give your two cents there (and here too). I'm pinning this issue and referencing it on the repository for further reference.