revert to metis 5.1.0

[akhmerov]

Closes #106

Checklist

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

[conda-forge-webservices]

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.

[akhmerov]

@minrk @traversaro this seems to be fairly straightforward, and the build is passing. I've left the metis patch in the repo for future use.

[minrk]

This will work. Once conda-forge/conda-forge-pinning-feedstock#5397 propagates, specifying the version in meta.yaml shouldn't be necessary and the updated pin should be applied by a rerender.

[akhmerov]

Ah, does it mean I should remove the pin?

[minrk]

Depends on if you want to wait an hour or two for conda-forge-pinning to propagate :)

[minrk]

Actually, looks like it's ready now. Removing the pin and rerendering applies the 5.1.0 pin

[minrk]

When this lands, do folks think we're ready to start the migrator for mumps itself? conda-forge/conda-forge-pinning-feedstock#5274