Add migration for eigenpy3103

[olivier-roussel]

Checklist

• Used a personal fork of the feedstock to propose changes

As noted in the migrator file, eigenpy must be added to global pinning once migration complete

[conda-forge-admin]

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/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ top-level output has some malformed specs:

• In section test: python >= 3.8 Requirements spec fields should always be space-separated to avoid known issues in conda-build. For example, instead of name =version=build, use name version build`.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13635224353. Examine the logs at this URL for more detail.}

[xhochy]

Please directly add it to the global pinning, otherwise it will not be updated automatically.

[olivier-roussel]

Should we create an updated migrator for current eigenpy version instead (v3.11.0) or migration will be done automatically once this PR merged ?

[conda-forge-admin]

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

I was trying to look for recipes to lint for you, but it appears we have a merge conflict. Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.