Updating log levels analyzer to allow usage of split

[manumafe98]

closes #150

I have a couple of doubts about this:

• Naming of the new comment
• If I should pass the list to the comment as a parameter, so we do not hardcode the methods in the comment of website-copy and instead use a variable (if possible, because I only use it with strings, so Im not sure if its possible)

Related to the second point, I guess I could create a method to format the elements of the list in a string that looks the likes of: "substring, split" but if we take that decision, we should extract that logic from the analyzer? so then we can reuse it with another analyzers in the future? or we dont mind repetition in this case

[sanderploegsma]

I'm wondering whether this approach makes it a bit too complex. Can't we decide to recommend using either substring or split in the comment (so not to mention both methods but one of the two, whichever we prefer) and update the analyzer implementation to follow these rules:

Scenario	Analyzer output
Solution using substring	N/A
Solution using split	N/A
Solution using some other approach	Use substring method*

* Or split if we think that's better than using substring

[manumafe98]

I'm wondering whether this approach makes it a bit too complex. Can't we decide to recommend using either substring or split in the comment (so not to mention both methods but one of the two, whichever we prefer) and update the analyzer implementation to follow these rules:

Scenario Analyzer output
Solution using substring N/A
Solution using split N/A
Solution using some other approach Use substring method*

• Or split if we think that's better than using substring

Sure, we can still use the same comment to recommend using substring then when we detect that neither split or substring has been used