FIX: Try to unpin mpich after new version available.

[hhslepicka]

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.

Trying to unpin after work done for conda-forge/mpich-feedstock#56

[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.

[hhslepicka]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.

[hhslepicka]

Rebased to pick up the latest release info.

[leofang]

The mpich fix is in, let's give it a shot

@conda-forge-admin, please restart ci

[hhslepicka]

@leofang it looks like it did it! Thanks for restarting CI here.

[leofang]

Cool! Perhaps you'd like to clean up the workarounds you added (fake-bin etc)?

[hhslepicka]

I will try to remove the fake-bin one but it was related to osx issue with cc1 that was not found somehow.

[leofang]

Ah I see, I thought it was for fixing the OS X build. nvm then.

[hhslepicka]

@leofang for reference, the cc1 issue comes from here: conda-forge/gfortran_osx-64-feedstock#11 and the workaround from here https://github.com/awvwgk/staged-recipes/tree/dftd4/recipes/dftd4