Add BlockingReferences test (failing for now) that reveals #379

[KvanTTT]

Potentially fixed by #385

[AppVeyorBot]

❌ Build ConfuserEx 851 failed (commit c04ea1dd28 by @KvanTTT)

[AppVeyorBot]

❌ Build ConfuserEx 853 failed (commit 85b170a39b by @KvanTTT)

[KvanTTT]

@mkaring do have any idea how to fix it?

[mkaring]

Okay, so I found the reason why this is breaking. The issue is the way the renamer processes different assemblies. It does that currently in sequence and there is nothing I can do about that for now. What it needs to do is process all assemblies at once so it can rename the members in proper sequence.

This can't be done without some major reworking. So I "fixed" this, by having ConfuserEx detect this issue and blocking the renaming for all members affected by it. This fix is now in #425
That is the best I can come up with right now.

A better solution would be to delay the renaming for parts of an assembly until after another assembly has been processed.