Disable Java Map accessing by properties

[tuchida]

Closes #820
This will have an impact on these Pull Requests. #824, #827

---

#713 had compatibility issues because entry access by properties took precedence over Java methods. If Java methods are prioritized, compatibility issues will probably disappear.
But here's what happens.

// Java
public Map getMap() {
    return new TreeMap();
}

// Rhino
var m = Foo.getMap();
m.firstKey();  // TreeMap method

getMap returns java.util.Map, but an instance of it is java.util.TreeMap, so you can use the java.util.TreeMap method. If Java methods are prioritized, in order to access it by property, you need to avoid the TreeMap method instead of Map. You always need to know what the instance is. Also, if getMap returns a different Map implementation, your existing code may not work.

---

Nashorn has probably extended the use of indirect-eval-call to distinguish between property access and method invocation. I'm also checking for behavior such as the distinction between m[0] and m['0'], and that Java methods are not JavaScript Functions.

[gbrail]

I think that this is the next PR that we should merge as we make List and Map work better. Can you please take a look at a few improvements? Thanks!

[gbrail]

"getContext" will throw a RuntimeError if there is no Context on the stack. That's usually incorrect but I know that there's code out there that might do it. Could you please replace these tests with:

Context cx = Context.getCurrentContext();
if (cx != null && cx.hasFeature(Context.FEATURE_ENABLE_JAVA_MAP_ACCESS))

(or make a helper function in Context or ScriptRuntime since we do that ll the time!)

[tuchida]

dc43827
I fixed NativeJavaMap and NativeJavaList since I based it on #713.

[gbrail]

Yes, those changes help. Thanks!