implement type() on ArithmeticBinaryExpr instead of its children

I think these individual implementations of ::type() must have been a hangover
from when we tried to get precise about Range types yielded from such
expressions. Now that we treat the result of any arithmetic operation as the
unbounded range type, these implementations are all identical and there was no
point to duplicating them.