[WIP] Use Poetry as the dependency manager of this library

[bitterteriyaki]

Pull Request check-list

• Do tests and lints pass with this change?
• Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
• Is the new or changed code fully tested?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Is there an example added to the examples folder (if applicable)?
• Was the change added to CHANGES file?

Description of change

Use Poetry as the package manager of this library.

Checklist

• Migrate all the fields from setup.py to pyproject.toml
• Update CI workflows
• Maybe put all configuration files from another libraries (e.g. .flake8, .isort.cfg, etc.) into pyproject.toml?
• Update CONTRIBUTING.md file
• Update documentation and README.md

[bitterteriyaki]

Is this a good time to upgrade the outdated dependencies (including dev deps)?

[bitterteriyaki]

I took a little liberty to add some improvements to the workflow. If you don't like it or want any changes, don't hesitate to leave feedback. 😄

• I changed the job name and added names to all steps
• I changed the workflow name
• I moved the permissions object to its respective job

I did not tested this workflow yet, it can be broken.

[bitterteriyaki]

I'm getting some conflicts from the docs/requirements.txt dependencies. The ipython library needs Python 3.10+ but this project has support to Python 3.8. I'll wait any maintainer to answer how to proceed in this situation.

[akx]

I wouldn't use Poetry for library packaging – it might be OK for applications, but I don't think it's the best fit for libraries.

Please also see #1658 for previous discussion.