feat: STFT-57 - Prompt for update on linter version mismatch

[AldosAC]

This PR implements a check during a scan which determines if the current configuration is out of date with the configuration SeCureLI expects.

This check will determine there is a mismatch if you modify the .secureli.yaml file, or if the .pre-commit-config.yaml file is modified directly.

If it detects a mismatch, the user will be prompted to update to the expected configuration. If they decline, then the scan will be aborted.

If the mismatch is caused by a linter being added or removed, then SeCureLI will inform the user and indicate which linters were removed, or added unexpectedly.

If the mismatch is caused by a linter version being different, then secureli will notify the user which linter and will indicate which version it expected to find and what version it actually found.

Testing this PR should be fairly straight forward, any change to the .pre-commit-config.yaml file in the root directory will trigger the update request. You can change linter versions, remove linters, or any combination that you like and you should see the prompt to update when you attempt to perform a scan.

Note: There are a bunch of pycache files that are deleted as part of this PR. When this repo was migrated from BitBucket, the .gitignore file was not included, so the cache files were committed. These files should have been ignored, so I removed them while I was working on this PR.

[centenor]

Prompt works as expected, but it looks like it's returning the same hash? I imagine those two values would be different

[AldosAC]

Great catch, that is absolutely a bug. Let me get that squared away!

[centenor]

If someone manually updates the value in the pre-commit config yaml and then tries to push that update, should this feature block that commit?

[AldosAC]

No, this doesn't block any commits containing a modified .pre-commit-config.yaml file. It would notify anyone with a modified .pre-commit-config.yaml that the configuration is not what secureli expects though. So if a team member did commit the pre-commit file and other team members pulled that file, they would all receive warnings that the configuration does not match what secureli expects.

[centenor]

Not sure if something changed, but now whenever I run a secureli scan after changing the value of something like black in the .pre-commit-config.yaml nothing gets flagged. Is that intended?

[AldosAC]

@centenor - Are you still having issues with it detecting changes now?

[AldosAC]

I spoke with Raul offline and he confirmed the error was the result of using the wrong venv to test and that the application is working as expected.

[khollerman]

Currently this part of the AC is not being met: "Linter versions can be upgraded OR downgraded."

An acceptance of the update prompt is reverting back to the base version prior to running the scan.

[khollerman]

Looks good