Issues like #4581 come up when everyone (including CI) is running on devices that support the latest and greatest. There are issues on older devices which don't support everything. We have multiple paths right now that are completely untested in practice because everyone has new, powerful machines. I only discovered this one as I had an ancient lavapipe installed.

We should expose some way so that the backends can force these features off, so the testing harness can run again with all of it disabled. Additionally we should run with as many features exposed as we can, just private capabilities which cause different code paths to be taken should be disabled.

This might be either a request adapter flag, instance flag, or a method on the device itself.