STRICT_EXPECTED_CALL should also take function pointers

The following code is valid:
```c
MOCKABLE_FUNCTION(WINAPI, BOOL, mocked_PathFileExistsA, LPCSTR, pszPath);
...
STRICT_EXPECTED_CALL(mocked_PathFileExistsA(TEST_FOLDER));
```

The following code is NOT valid:
```c
MOCKABLE_FUNCTION(WINAPI, BOOL, mocked_PathFileExistsA, LPCSTR, pszPath);
...
static BOOL(WINAPI *pfPathFileExistsA)(LPCSTR path) = mocked_PathFileExistsA;
STRICT_EXPECTED_CALL(pfPathFileExistsA(TEST_FOLDER));
```

even when pfPathFileExists is a pointer to mocked_PathFileExistsA, the code should compile...

Best Regards,
Andrei Porumb

Start by tracing the STRICT_EXPECTED_CALL macro and reproducing the difference between a direct mocked function call and the pfPathFileExistsA function-pointer call shown here. The work is done when the pointer form compiles while the existing direct-call form continues to work.

Written by the indexing model from the issue text.