A couple places where InterfaceContract is not established on reference when it's not calculated by introspection

The vtests have a couple examples which result in component references being created without a corresponding InterfaceContract.

This is not a problem with the current default binding impl (as these tests are currently passing), but a switch to using the WS binding, say, shows the issue.

I'll attach a patch, too, but here are the issues:

------------------------------------------------------------------------------
In vtest/java-api/apis/componentcontext:

return componentContext.getService(DComponent.class, "dReference").getName();

In vtest/java-api/annotations/reference

public class AServiceImpl implements AService {
....
public BService b4; // field injection (public, un-annotated)
------------------------------------------------------------------------------

In both cases, the SCDL merely configures the ref target (and binding) but does not define the ref intf.

I haven't given this area a great deal of thought, my guess is we want to extend our Java introspection capabilities, though I could see that for some impl
types the better answer might be to require the SCDL to configure the intf in component SCDL.

I didn't try the latter either, but wanted to just write up the issue for now.

Thanks,
Scott