ensure all mpi builds of metapackage are uploaded

[minrk]

closes #170

this doesn't solve the problem in general because we'll need every dependency for which we have multiple variants included here, but it should be enough for now.

I took the opportunity to remove the run_constrained requirement from the components, which make a circular restriction. This is based on discussions around a possible new release of legacy fenics, and these prevent making a release of a partial package, where dolfin 2023.1 might depend on the existing dijitso 2019.1, without needing a coordinated release of everything.

[conda-forge-webservices[bot]]

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.

[minrk]

To confirm the fix, check that the build ids for two builds for the same Python+platform are different, e.g.

• https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=648351&view=logs&j=9a864fd9-6c8f-52ca-79ce-2aa6dca1a1de
• https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=648351&view=logs&j=696704cc-6fef-57a3-ea36-f27779b8cd5e

which are both linux-64/py311

[minrk]

fix confirmed, should be all set when CI finishes

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!