[clang-tools-extra] [clang-tidy][readability-identifier-naming] Resolve symlinks for checking style for file (PR #81985)

[Dmitry Polukhin via cfe-commits]

dmpolukhin wrote:

> This problem seems like it should be handled globally, not in a single specific check. IIUC any check that reads options from the .clang-tidy file is affected.

Yes, but the majority of checks ignores the problem but `readability-identifier-naming` handles styles per file so improving logic here makes sense to me. About general issue with checks being selected by main file there are several discussions as far as I know without clear direction that all agreed.

> What build system are you using, bazel? We use it and don't have any problems. If your build system creates a sandbox, you need to make sure clang-tidy is also executed from within that sandbox.

I'm talking about Buck in some configurations but I think Bazel also should be affected. Projects with more unified styles usually significantly less affected because .clang-tidy config in higher level can be found and used in some cases.

https://github.com/llvm/llvm-project/pull/81985