• Reversed secret scanning location matching to loop through target locations instead of source locations. As mentioned in [gei] Secret scanning alert matching logic might need to be reversed for locations #1238, it is expected that this tool will be used at the back of a repo or org migration, and therefore, the number of alerts and number of locations for each alert at the source will always be greater or equal to the ones at the target as not everything gets migrated.
• Fixed a secret scanning debug traces showing incorrect target alert number
• Separated the logic doing the location matching into its own function.
• Added 2 test cases to test the logic for location matching

• Did you write/update appropriate tests
• Release notes updated (if appropriate)
• Appropriate logging output
• Issue linked
• Docs updated (or issue created)
• New package licenses are added to ThirdPartyNotices.txt (if applicable)

Fixes #1238