Bindings type may check incorrectly when the declared type omits package qualifier

BIND variable delcarations which employ an initializer and a type name without a package qualifier may end up using the wrong type for the BIND var e.g. given classes org.my.Foo and org.my.FooBar

BIND foo : Foo = $0.returnMeFooBar()

may use the return type org.my.FooBar of method returnMeFooBar() as the type for foo even when it bears no relation to Foo.

This only happens when Foo is unknown at the point the binding is type checked i.e. when none of the other preceding elements of the rule provide type information which allows the bare name Foo to be associated with the package qualified name org.my.Foo and hence resolved to a class of that name.

The fix should allow the resolved class for Foo to be inferred form the type of the initializer in such cases. For example, if the return type of returnMeFooBar() is x.y.Foo or is a class class org.my.FooBar which is a subclass of a class called x.y.Foo or an implementation of an interface claled x.y.Foo then the appropriately named class should be used to resolve the declaration type Foo.