Don't call computeKnownBitsFromRangeMetadata for extended loads --
this can cause a mismatch between the width of the !range metadata and
the width of the APInt's accumulating KnownZero (and KnownOne in the
future). This isn't a problem now, but will be after a future change.
Note: this can be made more aggressive in the future.