Update behavior of SA1501 when SA1503 is disabled

[sharwell]

This commit updates SA1501 to include special handling for the case where
SA1503 is disabled. In this scenario, statements are analyzed instead of
curly braces.

Fixes #1175

[sharwell]

📝 Not sure yet what causes this result from the code fix.

[Noryoko]

❓ What happens in this case for testCode?

if (i == 0)
    Debug.Assert(true); else Debug.Assert(false);

[sharwell]

In the updated implementation, I believe this does not report SA1501 at all.

[sharwell]

There are a couple remaining buggy behaviors in the code fix for this, but it does seem to work decently well overall. I'm a bit short on time so I configured the tests to detect the bugs as the expected behavior and left comments for review. Let me know whether you'd like to see them fixed before merging or if bug reports would be acceptable.

[Noryoko]

Since batchFixedTestCode now matches fixedTestCode should it be removed?

[Noryoko]

❓ Can you add tests for else and else if statements?

[Noryoko]

if (i == 0)
    Debug.Assert(true);
else Debug.Assert(false);

if (i == 0) Debug.Assert(true); else if (i == 0) Debug.Assert(false);

if (i == 0)
    Debug.Assert(true);
else if (i == 0) Debug.Assert(false);

if (i == 0) Debug.Assert(true); else if (i == 0) Debug.Assert(false); else Debug.Assert(false);

if (i == 0) if (i == 0) Debug.Assert(false); else Debug.Assert(false); else Debug.Assert(true);

if (i == 0)
    if (i == 0) Debug.Assert(false); else Debug.Assert(false); else Debug.Assert(true);

if (i == 0) if (i == 0) Debug.Assert(false);
    else Debug.Assert(false); else if (i == 0) Debug.Assert(true);

[Noryoko]

👍