[aws-cloudwatch] Input does not discover new log groups

We are using the `log_group_name_prefix` setting to discover multiple log groups under a certain prefix (e.g. /aws/eks or /aws/lambda). When e.g. a new log group is added, for instance due to bootstrapping of a new EKS cluster, filebeat has to be restarted manually to be able to capture the new logs into ES.