clang-tidy bugprone-argument-comment interaction with preprocessor macros / #define

An example like the following currently produces a warning with `bugprone-argument-comment` but most users should be surprised by this:

```
$ cat test.cpp
extern void print(const char *string);
#define LOG(message) print(/*string=*/message)
int main() {
LOG(/*message=*/"Hello World");
}

$ clang-tidy -checks=bugprone-argument-comment ./test.cpp
...
/home/matthiasb/test.cpp:4:7: warning: argument name 'message' in comment does not match parameter name 'string' [bugprone-argument-comment]
4 | LOG(/*message=*/"Hello World");
| ^
/home/matthiasb/test.cpp:1:31: note: 'string' declared here
1 | extern void print(const char *string);
| ^
```

Would be neat if it could match for the macro parameter names instead of the parameter names after substitution...

Start by reproducing the warning with the test.cpp example and the clang-tidy bugprone-argument-comment check. Trace how the check handles the LOG macro invocation and compare its behavior with the macro parameter names; done means the example no longer reports a false mismatch while ordinary argument comments remain checked.

Written by the indexing model from the issue text.