More robust 652-deopt-intrinsic.

The deoptimization check was flakey, as deoptimizations could
happen in other threads or prior to executing the loop method.

So instead, just ensure the method that used to deoptimize never
moves to being interpreted.

Test: 652-deopt-intrinsic
Change-Id: I035d87014b9d233fdaa40736501b7aac38a74f89