CRAVEX-integration: Integrate DejaCode with issue trackers

[pombredanne]

It would be great to have integration with various issue tracking system such as JIRA, GiThub and similar
Integrating with issue tracking tools is essential to integrate CRAVEX in existing workflows.
Ticketing systems are important workflow tools and integration with them, especially with existing workflows, is useful to provide easier adoption.

[DennisClark]

New Request Template Address Vulnerabilities in Product Packages created in DejaCode reference data to provide an example of a pertinent Request subject to integration with an issue tracker.

[DennisClark]

Proposed new field on Request Template:
name: Issue Tracker
type: dropdown list with GitHub, JIRA, Gitlab, Forgejo, Sourcehut as choices
help text: Identify an issue tracking application used by your organization to process a request.

Alternatively,
(1) Define the new field at the Dataspace level rather than the Request Template, and
(2) Introduce a new boolean checkbox on Request Template, defaulting to false, "Integrate with issue tracker".

[DennisClark]

Proposed new field on Product:
name: Codebase Repository
type: URL to a codebase repository
help text: Repository for the codebase associated with this Product

[DennisClark]

Proposed new field on Request Template:
name: Issue Tracker ID
type: URL to Issue in tracking application
help text; Link to associated issue in a tracking application, provided by the integration when the issue is created.

[DennisClark]

Use Case: Initiate Request to Address Vulnerabilities in Product Packages

A software product administrator reviews a product definition in DejaCode and identifies software vulnerabilities in several packages in the product inventory. Creates a Request (for example, using the Request Template Address Vulnerabilities in Product Packages) to be assigned to a member of the original product team. This initiates the integration process to create an issue in the associated tracking application (for example, GitHub, see #349 ) using that app's API, mapping the various pertinent DejaCode fields as possible. A successful execution of the API returns the tracking application Issue ID (as a URL) and updates the DejaCode Request.

Followup use cases:

• Updates to the issue in the tracking application are sent to the DejaCode Request API.
• Updates to the issue in DejaCode are sent to the tracking application API.

[DennisClark]

We'll probably need a small application to define the mapping of data between AboutCode applications (since we may expand this integration to ScanCode.io) and issue tracking applications. We should document that in #345