Handle "leapfrog" case for --audit

[domanchi]

Bug

When applying an audit, to an already audited baseline, users may find themselves in a strange case: through a combination of skips and decisions, secrets may be overridden in the baseline accidentally.

This should not happen.

Testing

detect-secrets$ detect-secrets --audit .secrets.baseline
<User enters: "y, s, s, n" respectively>
detect-secrets$ detect-secrets --audit .secrets.baseline
<User enters: "y, s, y" respectively>

You would expect that the output is like the below illustration:

secretA: TRUE
secretB: TRUE
secretC: SKIP
secretD: FALSE
secretE: TRUE

However, it would have actually ended up as follows:

secretA: TRUE
secretB: TRUE
secretC: SKIP
secretE: TRUE

[KevinHock]

LGTM