Restrict the pre-declaration usage of local variables detector (variable-scope) to Solidity 0.4

[CodeSandwich]

Describe the desired feature

The pre-declaration usage of local variables detector checks a property which is impossible to violate since Solidity 0.5, see the last point of the 0.5 changelog. The exploit scenario example doesn't even compile with Solidity >=0.5. Any variable-scopes found when using Solidity >=0.5 are obviously false positives and unfortunately the detector does that quite often. All it takes is a function with the same variable name used twice in two separate scopes, e.g.

function foo() public {
    {
        uint a = 0;
    }
    {
        uint a = 1;
    }
}

It'd be great if this detector was disabled altogether when analyzing codebases using Solidity >=0.5.

[montyly]

Hi @CodeSandwich , that's a good point. We have to update the detector

[0xalpharush]

My mistake this wasnt fixed in the linked pull requests

[0xalpharush]

closed by #1731