Partially work around pending deprecation of pkg_resources

[adrianeboyd]

Description

• Replace pkg_resources with importlib_metadata for spacy info
• Move pkg_resources imports for requirements check into individual methods and catch the deprecation warning in the test suite

Types of change

?

Checklist

• I confirm that I have the right to submit this contribution under the project's MIT license.
• I ran the tests, and all new and existing tests passed.
• My changes don't require a change to the documentation, or if they do, I've added all required information.

[adrianeboyd]

This is primarily to test the changes to spacy info, which are easier than the project requirements check.

Some of the project requirements check options:

• drop requirements check entirely
• vendor pkg_resources
• implement our own limited version checks that more or less do the same thing as the current checks

[rmitsch]

implement our own limited version checks that more or less do the same thing as the current checks

I think that's the cleanest option, but I'm not sure how much of an effort that would be. Disabling the requirements check as in this PR is fine for now IMO, I suggest to do the actual fixing of the package checks in a separate PR.

[adrianeboyd]

I think this is the best workaround until we can decide what to do about the requirements check. I don't know when this could potentially be removed from setuptools entirely.

People can import spacy without deprecation warnings.

Most people running spacy project run won't notice deprecation warnings.