This reorders existing transforms to put demanded elements last. The reasoning here is that when we have an example which can be scalarized or handled via demanded bits, we should prefer scalarization as that doesn't require dropping flags on arithmetic instructions.
This doesn't show major changes in the tests today, but once I add support for fast math flags to dropPoisonGeneratingFlags this becomes glaringly obvious.
The index types here differ because we don't canonicalize either way, and depending on transform order we can get either. D115387 adds the canonicalization, but I'd prefer not to block this patch on that one.