Add CICD Tool Discovery Plugin to Backend

[g-marconet]

Adds a CICD Tool Discovery plugin to the backend

Description

• Makes a best effort to identify CICD tools based on config file conventions.
• Currently supports:
  • AWS CodeBuild
  • BitRise
  • CircleCI
  • Electron Forge
  • Github Actions
  • Gitlab CI
  • Jenkins
  • Teamcity
  • Travis CI

Motivation and Context

• Knowledge of CICD tool used by a given repository can inform security decisions

How Has This Been Tested?

• Working in dev environment

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation change

Checklist

• My code follows conforms to the coding standards.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[davakos]

I know this is the JSON output I proposed for this plugin, but this was just a swag - please review just to ensure that it complies with output from similar APIs in the system... for example, scan_options.plugins in a scan object is just just an array of the internal plugin ids (no display name), and we maintain an internal mapping in backend & UI to the display names. Would this be a better and more consistent approach?

[g-marconet]

I don't think a scan_options.plugins type mapping would make sense in this context, but I also don't have a good grasp of what you are envisioning there. At a minimum, it would have the added complexity of causing us to have to edit things in two places when we want to add additional CICD tools or modify the current ones.

The current pattern is similar to the one in the repo healthcheck plugins, where there's an ID for the particular finding and then the plugins also provide a plaintext display_name analogue that eventually gets displayed in the UI. It keeps everything localized in the plugin, so changing things is more intuitive, IMO.