The semantics of the ops that implement the
OffsetSizeAndStrideOpInterface is that if the number of offsets,
sizes or strides are less than the rank of the source, then some
default values are filled along the trailing dimensions (0 for offset,
source dimension of sizes, and 1 for strides). This is confusing,
especially with rank-reducing semantics. Immediate issue here is that
the methods of OffsetSizeAndStridesOpInterface assumes that the
number of values is same as the source rank. This cause out-of-bounds
errors.
So simplifying the specification of OffsetSizeAndStridesOpInterface
to make it invalid to specify number of offsets/sizes/strides not
equal to the source rank.