Support yaml lists in the configuration values

[BraisGabin]

This issue is a continuation of #2463. There we talked about ForbiddenImports but we should generalice that solution to the rest of lists that we have in our yaml config file. (This case was implemented already #2474).

The reason for doing this is:

• It's easier to mantain the configuration using lists than strings
• We don't need to handle strange cases splitting strings (empty strings and similar)

The idea is to allow the use of yaml list where we are now using a string with ,. And if all goes well remove we can remove this old way in 2.0.

This is the list of configurations that, in 1.7.0, are lists splited by ,:

• *>excludes
• ComplexMethod>nestingFunctions
• ExceptionRaisedInUnexpectedLocation>methodNames
• ForbiddenClassName>forbiddenName
• ForbiddenComment>values
• ForbiddenImport>imports
• ForbiddenMethodCall>methods
• ForbiddenPublicDataClass>ignorePackages
• FunctionOnlyReturningConstant>excludeAnnotatedFunctions
• LabeledExpression>ignoredLabels
• LateinitUsage>excludeAnnotatedProperties
• LongParameterList>ignoreAnnotated
• MagicNumber>ignoreNumbers
• SwallowedException>ignoredExceptionTypes
• ThrowingExceptionsWithoutMessageOrCause>exceptions
• UnnecessaryAbstractClass>excludeAnnotatedClasses
• UseDataClass>excludeAnnotatedClasses
• WildcardImport>excludeImports

[BraisGabin]

All the PRs are done now :)

[arturbosch]

Great work!