Add Project and Codescan Identifier fields to Conclusions file

[mjherzog]

We need to add Project and Codescan Identifier fields to the Conclusions file for grouping Conclusion files by Project and tracking a Conclusions file back to the corresponding scan file/activity. Some key design assumptions / questions are:

• Both fields are labels, i.e. not validated.
• The overall logic is that one AboutCode Project may have multiple Codescan Identifiers where the latter identifies a Scan/Conclusions file. The use case is that there may be multiple Scan/Conclusions files - e.g. where the product codebase is in multiple repos.
• Both fields should be stored at the Conclusions file level for ease-of-use and consistency across a Scan/Conclusions file.
• It may make sense to enter/generate either or both fields during a scan where you might specify the Project in your scan parameters and ScanCode generates a Codescan Identifier.
• For Codescan Identifier we need to think about possible confusion between an internal identifier in the Scan/Conclusions file versus the external filename.

[mjherzog]

Closing because we are deprecating the Conclusions feature.