Print mutation details on inlined code detection warning

[Vampire]

No description provided.

[Vampire]

I updated this PR to latest master, maybe you have time for it now. :-)

[hcoles]

This will make the log even more noisy. There isn't really an action the user can take when this occurs (beyound raising an issue) so it was probably incorrect to make it a warning in the first place. If you can update it to be a debug message I'll merge it in.

[Vampire]

I don't fully remember as it is 3 years ago.
But back then I probably greatly missed this information and needed it to properly process without much debugging.
Also, this additional info is on a warning.
Warnings are hopefully not happen that often and if they happen, the average developer should try to get rid of them and welcome to have the necessary information for that. :-)

Ok, that was a lie, the average developer ignores warnings, but don't destroy my dreams. :-D

[Vampire]

Yeah, it's still the same.

13:10:23 PIT >> WARNING : Found more than one mutation similar on same line in a finally block. Can't correct for inlining.
13:10:23 PIT >> WARNING : Found more than one mutation similar on same line in a finally block. Can't correct for inlining.
13:10:23 PIT >> WARNING : Found more than one mutation similar on same line in a finally block. Can't correct for inlining.
13:10:23 PIT >> WARNING : Found more than one mutation similar on same line in a finally block. Can't correct for inlining.

with no way to see what might be the problem to at least be able to report it properly.

[Vampire]

If you are concerned about the noise, how about adding the details only in VERBOSE and VERBOSE_NO_SPINNER?