fix is_zero detection on Mul._eval_is_* tests

Once a None is obtained for is_zero, it should no longer be updated.
The return value must consider the value of is_zero. This can
change if S.Zero.is_imaginary = S.Zero.is_real = True is ever true.

The routines were shortened a bit, too.
nonzero has been merged into zero; neither routine was completely right and failure occurred if either one of them were commented out. All tests pass with the version of is_zero that is present now.