Refactor AnnotationRule to improve maintainability

[paul-dingemans]

Description

Replace (biggest part of) processing of MODIFIER_LIST and FILE_ANNOTATION_LIST with processing of
individual ANNOTATION_ENTRY. This allows ANNOTATION_ENTRY to be followed by EOL_COMMENT plus
another ANNOTATION_ENTRY:

@Suppress("AnnotationRule") // some comment
@Bar
class Foo

Closes #1539

Annotation with parameter(s) on same line as annotated construct is rewritten to
annotation on a separate line directly as otherwise a lint violation would remain
after the first format.
Before format:

@Suppress("AnnotationRule")class FooBar {
    @Suppress("AnnotationRule")var foo: String
    @Suppress("AnnotationRule")fun bar() {}
}

After format:

@Suppress("AnnotationRule")
class FooBar {
    @Suppress("AnnotationRule")
    var foo: String
    @Suppress("AnnotationRule")
    fun bar() {}
}

Detect a single annotation without parameters on same line as annotated construct while the annotation is preceded by another annotation with parameters on a separate line:

class FooBar {
    @Foo("foo")
    @Bar val bar: Any
}

and format it as

class FooBar {
    @Foo("foo")
    @Bar
    val bar: Any
}

Detect lines with multiple annotations while another line also contains an annotation:

@Foo1
@Foo2 @Foo3
fun foo() {}

and format as:

@foo1
@Foo2
@foo3
fun foo() {}

Reword the violations to be more clear.

Checklist

• PR description added
• tests are added
• KtLint has been applied on source code itself and violations are fixed
• documentation is updated
• CHANGELOG.md is updated

In case of adding a new rule:

• Rule is added to rules documentation