Making address sanity check in parseCommandPattern() less strict: Let parseCommandPattern() trigger a parse error in case the address is not found only in case cntxt->nspace->isAtomModule, i.e., only when malAtomProperty() needs to be called.
Making address sanity check in parseCommandPattern() less strict:
Let parseCommandPattern() trigger a parse error in case the address is not found
only in case cntxt->nspace->isAtomModule, i.e., only when malAtomProperty()
needs to be called.

Other cases seems to be handled by the mal interpreter in
monetdb5/mal/mal_resolve.mx:findFunctionType(),
yielding a "object code missing" error message.

This make the following tests work, again, as they did before adding this
sanity check in the first place:
monetdb5/mal/Tests/tst102.mal
monetdb5/mal/Tests/tst104.mal
monetdb5/mal/Tests/tst105.mal
monetdb5/mal/Tests/tst105a.mal
monetdb5/mal/Tests/tst106.mal
monetdb5/mal/Tests/tst115.mal
monetdb5/mal/Tests/tst150.mal
monetdb5/mal/Tests/dynamicload.mal

zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb,zyzyis/monetdb