Adding !range to a call instruction to communicate the possible range of the return value (analogous to !range on loads) already works in LLVM today, we just need to use it. Fixes the test case in #49572 and we already have the information anyway, so it's a cheap and easy win. cc @eddyb
