It was introduced after we moved to generating our auto-configuration and management context import files using an annotation processor. This didn't work out well and we reverted it (#31228). We can get rid of the ProcessedAnnotations plugin too as it doesn't really have any benefit at the moment and it's contributing to some deprecation warnings in the build.