Prepare for 0.2.0 release under new name

[nickray]

There has been confusion about whether solo-python supports Solo 2, and whterh solo2-cli supports Solo 1.

Hence, renaming this project, to make clearer its focus on Solo 1, only.

Generally:

• use solo1 (via pip install --upgrade solo1) to update Solo 1 devices and use their specific functionality
• use solo2 (via cargo install --force ---locked solo2) to update Solo2 device and use their specific functionality

For FIDO functionality, this is mostly independent of the device. solo2 does not have proper support for FIDO yet, as there is no good CTAP-library for Rust yet. So, you can use solo1 for this (e.g. solo1 key make-credential), or general-purpose tools like fido2-token.

Following release of solo1-cli on PyPI as solo1, I will make a final solo-python release which depends on the new package and is otherwise empty, following the approach recommended by https://github.com/simonw/pypi-rename.

At least for now, leaving the module solo inside this with its old name, to prevent dependees on solo-python as a library from breaking (:crossed_fingers:).

@conorpp @szszszsz