[Codegen] RemoveSingleIterationLoop should use ValueBoundsOpInterface or similar

[krzysz00]

Currently, RemoveSingleIterationLoop is using a half-baked, homegrown bounds analysis to get minima and maxima for the arguments to affine expressions.

ValueBoundsOpInterface is already set up for this, we should use it.

[krzysz00]

I suspect, implicitly, that the pass that annotates GPU IDs with their bounds will need to be moved up before said loop iteration removal - or we could start doing such annotating in-place.