[Feature] "Compile Active File" for headers

Request Overview

In CLion, I can do the equivalent of "Compile Active File" and it does something reasonable rather than failing saying there's no way to build headers (which is correct, of course, but useless).
To me, Something Reasonable is:

1. Find the same-named .cpp or .c file as close as possible in the file tree that has an #include that includes the header in question.
2. If that fails, look for ${basename}*.{cpp,c} that includes the header (this would find test-drivers for header-only includes.
3. If that fails, (e.g., for a header-only header), find the closest file in the file tree that #includes the header in question and build that.

That's the fancy way -- but better than nothing would be to find any .cpp file that includes the header in question and build that. In my mind, "Compile Active File" means "I want to see what the compiler makes of the file I'm looking at."

Related:

• #3709
• #3845

Additional Information

No response

The issue names no files or tests. Start by tracing the existing “Compile Active File” command and review related issues #3709 and #3845; define the source-selection behavior above, then verify the command builds a suitable includer for headers.