Co-authored-by: Kashif Khan <70996046+kashifkhan0771@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

* added godaddy detector

* added pattern test cases

* added integration test cases

* resolved comments

* added ote as keyword

* added non secret pattern for negative test case

* updated buildkite detectors

* resolved comments

* added scoped in extradata

We have recently seen panics when underlying readers panic (which can happen due to third-party library bugs). I'm not sure why the panics are new - it could be a case of bad luck, but there have also been recent changes to error handling. This is the smallest change that seems to fix a real problem but I'm not sure if it's the best global solution.

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

* rename

* update

* fix typo

* add config option for s3 resumption

* updates

* initial progress tracking logic

* more testing

* revert s3 source file

* UpdateScanProgress tests

* adjust

* updates

* invert

* updates

* updates

* fix

* update

* adjust test

* fix

* remove progress tracking

* cleanup

* cleanup

* remove dupe

* remove context cancellation logic

* fix comment format

* make resumption logic more clear

* rename

* fixes

* update

* add edge case test

* remove dupe mu

* add comment

* fix comment