Migrate from setup.py and setup.cfg to pyproject.toml

docs/internals/publishing.md

@@ -2,7 +2,8 @@
 
 A small note on how the linter is usually published to PyPi:
 
-- `rm -r django_migration_linter.egg-info/`
-- `pip install wheel twine`
-- `python3 setup.py sdist bdist_wheel --universal`
+- `rm -r django_migration_linter.egg-info/ dist/`
+- `pip install --upgrade build`
+- `python -m build`
+- `pip install --upgrade twine`
 - `twine upload dist/django_migration_linter-X.Y.Z-py3-none-any.whl dist/django-migration-linter-X.Y.Z.tar.gz`

docs/usage.md

@@ -92,7 +92,7 @@ You can also ignore backward incompatible migration tests by adding this option
 
 `python manage.py lintmigrations --exclude-migration-tests ALTER_COLUMN`
 
-The migration test codes can be found in the [corresponding source code files](../django_migration_linter/sql_analyser/base.py).
+The migration test codes can be found in the [corresponding source code files](../src/django_migration_linter/sql_analyser/base.py).
 
 ## Production usage example