* stripe payment intent detector added

* updated the stripe payment intent detector to verify the payment intents

* tests updated for stripe payment intent

* simplified code in the stripe payment intent detector

* fetch secrets from gcp

* updated stripe api return values for 400 and above cases

* fixed integration test

* updated the stripe payment intent detector keywords

* updated the stripe payment intent detector to store the client secrets against all keys

* simplified code

* improved the client secret verification logic

* Added support to scan github commit metadata for targeted scans

* added log

* add commit hash in context

* move context value adding to scanTarget

* added v2 log

- Change single quotes to double quotes for consistency
- Add a check to install `jq` if it is not already installed

Signed-off-by: Bo-Yi Wu <appleboy.tw@gmail.com>
Co-authored-by: Kashif Khan <70996046+kashifkhan0771@users.noreply.github.com>
Co-authored-by: Nabeel Alam <nabeelalam811@gmail.com>

* Added new version for heroku detector

* updated integration tests

* [fix] Report the unit in a single scan job

* Eliminate divide by 0 possibility

We have several metrics that have captured job ID as a dimension. This is, in a strict sense, "wrong" because the cardinality is unbounded, but our job counts have been low enough that we've been able to get away with it. However, recent exploration of a new distributed job technique has caused job counts to substantially increase, and this extra, "incorrect" dimension is now harder to justify.

We have been recently seeing some trouble with some of our Prometheus scrapes, and while I haven't drawn a direct connection between that trouble and the increased cardinality, I do know that we don't use the job ID dimension anywhere. We always sum it away! So this commit removes it. We're shouldn't be doing it, we're not using it, and it might be causing problems we're seeing.

This allows the underlying http request to respect the context

* Add config.proto

* Make protos

* Add ConfigurableSource implementation

* Parse config protoyaml into configured sources

* Refactor setting postman keywords into a helper method on the engine

* Add scan subcommand and plumb it all together

* Refactor ConfigurableSource to ConfiguredSource

* Export AhoCorasickCoreKeywords and return the set

* Disallow source configurations for non-scan subcommands

* Fix stdin scan compilation errors

* Rename command to multi-scan

* Add config file documentation

* Add more documentation for ConfiguredSource

* Replace initFunc closure with an embedded anonymous struct

* Assign directly to refs

* Fix typo

* Updated OpenAI Analyzer

* fixed test

* jira token analyzer init

* added api requests in jiratoken analyzer

* more apis added for jira resources

* removed unnecessary code

* added test for jira token analyzer

* repeat resources in analyzer result based on assigned permissions of jira token

* simplified the code

* updated secret manager for analyzer tests

* cleanup git commit validation

* fixed local git repo validation

* added remote commit validation

* removed remote repo commit validation