Add unit test to catch another bug in Boogie where FunctionCall ShallowType
is not correctly set. This is related to the bug fixed in cea703affa29. That
commit fixed the ShallowType when it was set using the constructor that takes
a Function but the parser uses the other constructor which has the same bug.
Fix FunctionCall.Resolve() so that when the function is resolved the type becomes availble via ShallowType().
This fixes the ExprTypeChecking.FunctionCallTypeResolved() unit test.