Allow checked/unchecked state of Licenses

[bs-jokri]

It should be possible to have licenses associated with a state that indicates whether this license is already gone through a clearing process. (Is required to mark licenses imported from other sources such as BDP)

[blaumeiser-at-bosch]

As a project developer I want to process an open source component with an unknown license without further approval so that the processing of the new licenses does not slow my project work down by approval processes.

Criteria for success:

• A new license can be added by a developer without the need to consult another person. This could be done by the import of the result file of a scan tool, or by manual entry of the license information using the ui. Any created license, be it in an automatic import or by a manual entry is marked as "unchecked".
• A license marked as "unchecked" can be used as any license, e.g., while creating release relevant artefacts (e.g. disclosure document).
• A license administrator can process the license and switch the state to "checked". This includes an approval of the license and a completion of the license information according to the organizations oss process, e.g., an approved list of obligations to follow.
• A project developer needs the possibility of a report, so that he can identify unchecked licenses and process them according to the organizations oss process.

Hint: The mechanism should be equal to attachments, as discussed in daily on Nov. 13th, 2017.

Hint: The feature as such does not imply any support towards a local process, i.e., the way unchecked licenses affect the release process of a project resp. the approval process of a license. The local processing of an unchecked license has to be defined in an organizations oss process and can only rely on the state information implied by this feature.