Make sure new effect check is correct by fuzzing against old effect check

Samir has run into an old effect check bug when scheduling gemv. It wasn't caught before because we haven't tested if the frontend bounds check still pass after scheduling. In theory it should pass, but it seems there is a discrepancy in old and new effect check.