umock_c_negative_tests_fail_call(i); should call umock_error when the call cannot be failed

At the moment umock_c_negative_tests_fail_call(i); will waltz unhindered doing "magic" if the "i"th call cannot be failed (such is the case of void functions).

umock_c_negative_tests_fail_call(i) shoul call umock_c_error hook in this case.

Start at the implementation and existing tests for umock_c_negative_tests_fail_call(i), then trace how the umock_c_error hook is invoked. Reproduce the void-function case and verify that attempting to fail an un-failable call invokes umock_c_error instead of proceeding silently.

Written by the indexing model from the issue text.