docs: Rename AsyncSubscriber to AsyncListener

Follow up to springwolf/springwolf-core#127

Author: timonback

docs/configuration.md

@@ -44,7 +44,7 @@ There are 2 ways to configure springwolf:
 
 It is recommended to structure the project such that all consumers and producers (classes containing listener/producer methods) are in the same package - it is not mandatory, and if they are scattered across multiple packages, just provide the highest in hierarchy package that contains all of them.
 
-The base package will be scanned for classes containing `@Component` annotated classes (that includes `@Service` annotated classes) for methods annotated with `@KafkaListener`, `@RabbitListener`, `@AsyncSubscriber`, `@AsyncPublisher`, etc.
+The base package will be scanned for classes containing `@Component` annotated classes (that includes `@Service` annotated classes) for methods annotated with `@KafkaListener`, `@RabbitListener`, `@AsyncListener`, `@AsyncPublisher`, etc.
 
 ### Info (required)
 

docs/documenting-consumers.md

@@ -10,23 +10,23 @@ Sometimes projects are configured in a way that makes Springwolf unable to autom
 For these use-cases, Springwolf provides additional ways to explicitly add them to the generated document.
 
 To document consumers, either:
-- add the `@AsyncSubscriber` annotation or
+- add the `@AsyncListener` annotation or
 - declare the `ConsumerData` object as part of the `AsyncApiDocket` or
 - rely on the auto-detection of `@KafkaListener`, `@RabbitListener`
 
-You are free to use all options together. Per channel and operation, first `ConsumerData` is used, then `@AsyncSubscriber` and last the auto-detected annotations.
+You are free to use all options together. Per channel and operation, first `ConsumerData` is used, then `@AsyncListener` and last the auto-detected annotations.
 
-## Option 1: `@AsyncSubscriber`
+## Option 1: `@AsyncListener`
 
-The `@AsyncSubscriber` annotation is added to the method of the listeners and extracts the payload from its arguments.
+The `@AsyncListener` annotation is added to the method of the listeners and extracts the payload from its arguments.
 Additional fields can be documented.
 
 The protocol operation binding is configured via `@AmqpAsyncOperationBinding` or `@KafkaAsyncOperationBinding`, which has to be on the same method.
 
 Below is an example to demonstrate the annotation:
 ```java
 @KafkaListener
-@AsyncSubscriber(operation = @AsyncOperation(
+@AsyncListener(operation = @AsyncOperation(
         channelName = "example-consumer-topic",
         description = "Optional. Customer uploaded an example payload",
         headers = @AsyncOperation.Headers(