Expanding these requires multiple constants. If we promote during type
legalization when they'll end up getting expanded in LegalizeDAG, we'll
end with larger constants. These constants may be harder to materialize.
For example, 64-bit constants on 64-bit RISCV are very expensive.
This is similar to what has already been done to BSWAP and BITREVERSE.
We should maybe expand parity as well to avoid an unneeded zero extend that SimplifyDemandedBits can't get rid of right now. Probably due to multiple uses. But we need to move ExpandPARITY from LegalizeDAG to TargetLowering first.