Optional fields to support `{riskassessment}`

[dgkf]

Developer day outcome:
Coalesce around a single reports package for both {riskassessment} and {pharmapkgs}

@AARON-CLARK @Jeff-Thompson12 - could you please jot down any features that a standalone reporting package would need to offer for you to leverage it in {riskassessment}?

For now, there's no need to consider where the right home is for any of these materials, we can strategize whether these are options, composable templates, etc. Let's start by just cataloging the different content that each use case might require.

[dgkf]

Just capturing the notes from our whiteboard during the session, we highlighted:

• how to store system information?
• how to handle manual review information
• dependency tree integration?

[llrs-roche]

Hi! Yes, so far we had in mind a more managerial role responsible to deciding if a package will be used or not and a more technical role evaluating or comparing the report with their internal report or (un)expected behavior to evaluate any differences.
The report so far doesn't have a way to include manual review information, but a new section can be created to have that, so decision taken on riskassessment are added to the report generated.
@AARON-CLARK @Jeff-Thompson12 Let me know if/when do you want to meet to talk more about this features.