Provide better error message when using :: in java_import (fixes #2074)
Fix defined?(::Object) logic in JIT. Partial fix for #2090.

The current IR for this logic uses the runtime helper call
isDefinedConstantOrMethod, which can trigger exceptions on its own
(if e.g. the method lookup triggers an error?). Because of that
handler, this bug in the JIT was caught and swallowed, resulting
in the defined? returning nil. That is not correct behavior; only
the exceptions we would expect to be raised by these lookups
should be caught.

In addition, I don't believe the :: form can be used to call
methods (::foo doesn't parse), so the use of exception handling
and isDefinedConstOrMethod may be inappropriate here.
Mark runtime_helper helper methods with JIT annotation.
[Truffle] +@ should be defined on Numeric.
[Truffle] Move #nonzero? to Numeric.
[Truffle] Move #times to Numeric.
[Truffle] Add missing "take nodes intro account" lines.
[Truffle] Move Fixnum methods belonging to Integer and Numeric.
[Truffle] Move Class#=== to Module and simplify assignableTo.
Expect j2ee tests to fail, awaiting #2091.
Revert to uncached super logic to fix #2092.

The cached versions of resolved super did not do appropriate arg
splatting as the old versions did. This will need to be remedied.

Also in this commit:

* Pulled out a generic path for all super compiles
* Added Null operand for a simple JVM null value
Actually implement Null in JIT.
Fix forced-compile loading of files.
Use instanceof for WrappedIRClosure here since next line is a cast to WrappedIRClosure.  It also reduces OperandType to be used only for persistence
Remove Null operand in favor of UndefinedValue.
Whoop forgot to remove import
CallInstr is always a ResultInstr.
Remove unused result param.
Some rearranging and consolidation of interpreter (trivial)
Update jnr-posix to 3.0.7-SNAPSHOT.