migrate to hatch + move importlib hacks to own module for typing

[RonnyPfannschmidt]

[RonnyPfannschmidt]

readthedocs seems to lack support for modern builds

[RonnyPfannschmidt]

fixed the issues, will need to add some docs later today

[RonnyPfannschmidt]

@pytest-dev/core this also serves as first example for going away from setuptools, please have a look

[RonnyPfannschmidt]

will squash locally after approval

[RonnyPfannschmidt]

Will reorder the commit content today to split the meaning

[RonnyPfannschmidt]

@nicoddemus i'd appreciat another look over before merging the split commits

[nicoddemus]

@bluetech good catch, I think you mean these places?

https://github.com/pytest-dev/pluggy/blob/70fde45e41370327da008ff052e1da10aa714c0f/.github/workflows/main.yml#L145

https://github.com/pytest-dev/pluggy/blob/70fde45e41370327da008ff052e1da10aa714c0f/.github/workflows/main.yml#L112

https://github.com/pytest-dev/pluggy/blob/70fde45e41370327da008ff052e1da10aa714c0f/.github/workflows/main.yml#L148

[bluetech]

Yes exactly. I'm not sure if we want to keep using the pypa/gh-action-pypi-publish action or switch to using hatch publish, I'll leave it to @RonnyPfannschmidt to decide.

[KOLANICH]

There is an issue: hatchling itself depends on pluggy.

[ssbarnea]

I am against this as I prefer setuptools-scm, but I will not block the change.

[RonnyPfannschmidt]

Hatch VCS uses Setuptools-scm

[RonnyPfannschmidt]

This is currently indefinitely blocked as the dependency loop with hatchling needs a resolution

[KOLANICH]

Do I understand right that only migration to hatchling is blocked, but the rest of changes ("move importlib hacks to own module for typing") are not blocked.