Migrate coverage configurations to pyproject.toml

[seisman]

Description of proposed changes

The project is using many different tools (e.g., black, coverage) and each tool may have many configurations, saved in different configurations files (e.g., .coveragerc, setup.cfg). PEP 518 introduced a standard configuration file pyproject.toml where tools can put their configurations.

This PR tries to migrate the coverage configurations from .coveragerc to pyproject.toml. We may migrate more configurations (e.g., black, pytest, setuptools-scm) in separate PRs.

Coverage configurations: https://coverage.readthedocs.io/en/latest/config.html

References:

• https://www.python.org/dev/peps/pep-0518/
• https://www.python.org/dev/peps/pep-0621/
• https://snarky.ca/clarifying-pep-518/
• https://snarky.ca/what-the-heck-is-pyproject-toml/

Reminders

• Run make format and make check to make sure the code follows the style guide.
• Add tests for new features or tests that would have caught the bug that you're fixing.
• Add new public functions/methods/classes to doc/api/index.rst.
• Write detailed docstrings for all functions/methods.
• If adding new functionality, add an example to docstrings or tutorials.

[weiji14]

This PR tries to migrate the coverage configurations from .coveragerc to pyproject.toml. We may migrate more configurations (e.g., black, pytest, setuptools-scm) in separate PRs.

Fully support this step-by-step move of all the configurations to pyproject.toml. Have a look too at https://python-poetry.org/ when you have time!

[seisman]

Have a look too at https://python-poetry.org/ when you have time!

Read a little bit about poetry, but it seems poetry still doesn't officially support dynamic versioning from setuptools_scm. See python-poetry/poetry#140, python-poetry/poetry#693, https://github.com/mtkennerly/poetry-dynamic-versioning.