Fail on ambiguous runtime function resolution without type information

[brynrhodes]

By default, ELM does not include type information, requiring the engine to resolve function overloads using runtime typing. However, not all engines perform runtime type resolution of functions, resulting in potentially ambiguous calls at runtime. For example:

define function TestAny(a Integer):
  a

define function TestAny(b String):
  b

define TestAnyFunctionWithInteger:
  TestAny(1)

define TestAnyFunctionWithString:
  TestAny('joe')

With runtime-typing, a correct evaluation is:

TestAnyFunctionWithInteger=1
TestAnyFunctionWithString=joe

The translator currently has options to output signature information (SignatureLevel on function invocations, but given the potential for runtime failure, it should be an error condition if this information is not included when there are potentially ambiguous runtime overloads as in the above example.