Remove use of setuptools_scm_git_archive

[dopplershift]

The .git_archival.txt in the sdist is breaking installation with new versions of pip (version comes up 0.0). Support for git archives is baked into setuptools_scm itself now with version 7.

Fixes #2053 using the removal of setuptools_scm_gitarchive identified as the root cause there.

[QuLogic]

LGTM if it all builds

[dopplershift]

Looks like we have some unrelated image test failures. I'm trying to get a PR together to fix that separately. That and #2056 should get CI green again.

[greglucas]

I checked this out, built an sdist and pip install *.tar.gz and it appeared to get the proper version now, whereas before checking out the sdist pip would get 0.0 for the version. So I think this is good.

[greglucas]

Do you want to backport this to the v0.20.x branch? I think this could be backported and then we could tag that commit as v0.20.2.post1 to get a new release out without needing to backport anything else.

[dopplershift]

@greglucas Done in #2059.

[jules-ch]

We should see if git archive install still works, excluding .git_archival.txt from sdist is necessarry but it might remove installation from git archive all together.

Anyway prioritizing pypi installation is right.

I think we need to file an issue in setuptools_scm aswell to at least document this or version inference priority.

Btw @keewis just saw this affects xarray sdist installation aswell.

[dopplershift]

It looks like pypa/setuptools_scm#734 is adding information to the docs (readme). My guess on reading it is that we have broken the version detection when installing from git archives.

My question: does this matter to anyone? I've never bothered with this on my other projects. We currently upload proper sdists to PyPI and that's what conda-forge points to. We haven't documented anywhere that people should consider installing from GitHub's auto-generated tarballs. 🤷‍♂️ I don't want to hold up getting a fixed PyPI sdist out for this, but I'd review and merge a PR that fixes it up.

[QuLogic]

Git archives can sometimes be useful if sdists are missing tests, but fortunately, Cartopy's sdists include tests, so we don't need to use the GitHub tarballs.

[jules-ch]

@dopplershift I'm ok with this +1
I recall seeing an issue in pint regarding this hgrecco/pint#1423.
But IMO there are work arounds.