[CIR][NFC] Fix test failures caused by double spaces in check line

[seven-mile]

The pattern call {{.*}} i32 mismatches call i32 due to double spaces surrounding {{.*}}. This patch removes the first space to fix the failure.

[seven-mile]

NOTE: The test failure occurs on two of my environments (Linux + Windows), but seemingly not on CI. Not sure about the reason. @advay168 Do you have any clue?😉

[advay168]

The expected output is something like call range(i32 0, 1024) i32 @llvm.nvvm.read.ptx.sreg.tid.x. I'm not sure why the range attribute isn't present in your environment.

[seven-mile]

Thanks for the clues! After investigation, I discovered that the range(i32 1, 65536) metadata is only attached to intrinsic calls when the NVPTX target is enabled. This metadata insertion is handled by the nvvm-intr-range pass.

Since this metadata addition occurs during mid-end optimizations, it falls outside the scope of CodeGen phase testing. This PR adjusts the CHECK lines to maintain consistency with the validation approach used in the OG counterpart.

[bcardosolopes]

Making tests for flexible sounds great, thanks!