fix: ClashingMemberRenamer incorrectly renames Enum types

[Yozer]

Problem

Fixes #1035

Solution

• Any comments on the approach taken, its consistency with surrounding code, etc.
• Which part of this PR is most in need of attention/improvement?
• At least one test covering the code changed

// few tests are failing, will take a look at them later...

[GrahamTheCoder]

Looks good. The failing tests probably just assert the old behaviour, which we now know is unnecessary, so you can just run them with recharacterize set to true.

[Yozer]

Yep, that's what I did.
I also compiled the new tests results to make sure that the not-renamed enum doesn't break them.

[GrahamTheCoder]

Hmm yes, good plan to check since I don't think the MultiFileCharacterization ones flag anywhere if the compilation of the result fails (whereas the normal ones output compile errors at the bottom of the output)