manually start PyPy migration

[mattip]

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [x] Bumped the build number (if the version is unchanged)
• [ ] Reset the build number to 0 (if the version changed)
• [x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [ ] Ensured the license file is being packaged.

The dependency resolver bot did not start the pypy3.8/3.9 migration because pywin32 is a parent in the graph. But I think pywin32 is an optional dependency for PyPy, not a hard one. The PR works around the problem by manually adding the migration file.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[mattip]

Any ideas why these three tests are failing to find the srcdir in shutil.copytree? Is that something known about pypy, windows, and jupyter_core?

FAILED tests/test_command.py::test_argv0 - subprocess.CalledProcessError: Com...
FAILED tests/test_migrate.py::test_migrate_dir - shutil.Error: [('C:\\Users\\...
FAILED tests/test_migrate.py::test_migrate_one - shutil.Error: [('C:\\Users\\...

[blink1073]

I'm not sure, we only test pypy on Ubuntu in CI.

[bollwyvl]

yerp: if we could figure out the right noarch invocation over on #49, we could save a lot of coal...

[mattip]

Outdated, closing