STRICT_EXPECTED_CALL should have an optional variable number of arguments to describe the call

Right now I have:
```c
STRICT_EXPECTED_CALL(create_something("a", 1));
```

But I want to have:
```
STRICT_EXPECTED_CALL(create_something("a", 1), "%s %d", "create_something for source", __LINE__);
```

And these printf-ish arguments would be printed in the get_expected_calls somehow as hints/pointers.

Start by tracing the STRICT_EXPECTED_CALL entry point and the get_expected_calls output mentioned in the issue. Review how the current call form is parsed and displayed, then define completion as accepting the optional printf-style description arguments and showing their resulting hint or pointer in get_expected_calls.

Written by the indexing model from the issue text.