Given the new all annotation use site target that is coming as experimental in Kotlin 2.2, it is inevitable to introduce a new, corresponding enum entry in KSP's AnnotationUseSiteTarget. While it won't break existing processors from ABI's perspective, it does:

1. break source compatibility and potentially runtime compatibility if all is encountered, and
2. make new processors which reference the new entry not binary compatible with older KSP implementations.

Implementation-wise, when getting annotations from synthetic elements, the originating element needs to be checked.