Ready for 0.1.0 PyPI/GitHub release #11

PyPI/GitHub rc-release preparation checklist:

• All PRs/issues attached to the release are merged.
• All the badges on the README are passing.
• License information is verified as correct. If you are unsure, please comment below.
• Locally rendered documentation contains all appropriate pages, tutorials, and other human-written text is up-to-date with any changes in the code.
• All API references are included. To check this, run conda install scikit-package and then package build api-doc. Review any edits made by rerendering the docs locally.
• Installation instructions in the README, documentation, and the website are updated.
• Successfully run any tutorial examples or do functional testing with the latest Python version.
• Grammar and writing quality are checked (no typos).
• Install pip install build twine, run python -m build and twine check dist/* to ensure that the package can be built and is correctly formatted for PyPI release.
• Dispatch matrix testing to test the release on all Python versions and systems. If you do not have permission to run this workflow, tag the maintainer and say @maintainer, please dispatch matrix testing workflow.

Please tag the maintainer (e.g., @username) in the comment here when you are ready for the PyPI/GitHub release. Include any additional comments necessary, such as version information and details about the pre-release here:

PyPI/GitHub full-release preparation checklist:

• Create a new conda environment and install the rc from PyPI (pip install <package-name>==??)
• License information on PyPI is correct.
• Docs are deployed successfully to https://<github-username-or-orgname>/<package-name>.
• Successfully run all tests, tutorial examples or do functional testing.

Please let the maintainer know that all checks are done and the package is ready for full release.

conda-forge release preparation checklist:

• Ensure that the full release has appeared on PyPI successfully.
• New package dependencies listed in conda.txt and tests.txt are added to meta.yaml in the feedstock.
• Close any open issues on the feedstock. Reach out to the maintainer if you have questions.
• Tag the maintainer for conda-forge release.

Post-release checklist

• Run tutorial examples and conduct functional testing using the installation guide in the README. Attach screenshots/results as comments.
• Documentation (README, tutorials, API references, and websites) is deployed without broken links or missing figures.