Do not run cargotest on quickcheck/proptest tests

[Manishearth]

As part of our CI we run "cargotest" on a variety of ecosystem crates, making sure they successfully build and run tests.

Unfortunately, some of use stochastic tests like quickcheck, which means that a crate passing our CI one day may not necessarily mean it passes CI the next. Perhaps we should audit the tests being run and filter out ones like these?

See #73511 (comment) and BurntSushi/xsv#227

cc @rust-lang/release

[Mark-Simulacrum]

Yeah I think we've discussed this to some extent previously within infra team as part of our "what to do about cargotest" discussions. cc @nellshamrell in particular

Not sure that we came to any conclusions though.

[XAMPPRocky]

Related: #70659

[ehuss]

The test_cat::prop_cat_rows test from xsv fails occasionally:

• Revert "Auto merge of #64823 - cuviper:min-std, r=Mark-Simulacrum" #65342 (comment)
• Validate builtin attributes for macro args. #88680 (comment)
• rustdoc: Remove String allocation in iteration in print_generic_bounds #92283 (comment)

[RalfJung]

This just bit me and took a lot of time as I triple-checked that after bors failing twice (!) in xsv, the same test actually works fine on my system.

[RalfJung]

The xsv test suite seems to be full of quickcheck tests, so I think the only way to fix this is to remove xsv from cargotest (or to only run a short list of curated tests).

[ehuss]

@RalfJung See #70659 where there is some discussion fo changing the cargotest set. I think the last comment implies dropping xsv.

[RalfJung]

Hm, that discussion seems to have stalled though.

So to fix the immediate problem, I propose we do something like #99602.