File annotations should be copied to `ClassBinarySignature`

[dovchinnikov]

Without this, file annotations are not considered when filtering the classes with non-public markers. Please find the reproducer in the attached pull request.

[fzhinkin]

File-targeting annotations (@file:..) seem to be only emitted for file-facade classes, and in all other cases, they are just lost.

If a file contains top-level declarations and has some @file-annotation registered as a non-public marker, a facade class generated to hold these declarations will be filtered out from the dump.

[dovchinnikov]

I understand how it behaves at the moment.

I'm arguing that non-public marker on file-level should affect the whole file, including types defined in the file.

[fzhinkin]

I mean, there's no info about such an annotation (except the file-facade case), so there's nothing we can do on the BCV side at the moment. Trying to figure out how @file-annotations are supposed to work (and if they are supposed to work the way they do).

[fzhinkin]

Corresponding YT issue: https://youtrack.jetbrains.com/issue/KT-64981

[shanshin]

As part of the migration of separate BCV functionality to Kotlin Gradle Plugin, the addition of new features to a separate plugin has been discontinued.

The issue moved to YouTrack.