mark mumps builds with metis 5.1.1 as broken

[minrk]

There were problems with metis 5.1.1, especially with regard to mumps. As a result, metis builds were rolled back to 5.1.0

So more recent builds of mumps are made with 5.1.0. I thought this would be enough, but due to solver priority preferring versions to build numbers (I think), metis 5.1.1, mumps-mpi 5.6.2-2 is still preferred to metis 5.1.0, mumps-mpi 5.6.2-4, as long as mumps-mpi is not directly requested (e.g. via fenics-dolfinx). So until a new version of mumps (or other packages) is built, the old metis 5.1.1 builds will still be picked up as the preferred solution.

More info:

• Crash with metis 5.1.1 mumps-feedstock#106
• halt metis 5.1.1 migration conda-forge-pinning-feedstock#5396

alternately, metis 5.1.1 itself could be marked as broken, but I'm not 100% sure that's right.

Checklist:

• I want to mark a package as broken (or not broken):
  • Added a description of the problem with the package in the PR description.
  • Pinged the team for the package for their input.

ping @conda-forge/mumps @conda-forge/metis

Package list found with:

from itertools import chain
from conda.gateways import repodata
from conda.core.subdir_data import SubdirData

for platform in ("linux-64", "osx-64", "osx-arm64", "linux-aarch64", "linux-ppc64le"):
    channel = repodata.Channel.from_channel_name(f"conda-forge/{platform}")
    d = subdirs.setdefault(platform, SubdirData(channel, f"repodata-{platform}.json"))
    for record in chain(d.query("mumps-mpi"), d.query("mumps-seq")):
        for dep in record.depends:
            if "metis >=5.1.1" in dep:
                print(f"  - {record['subdir']}/{record['fn']}")