Add "Preconditions" item about csaf

[tschmidtb51]

I see a couple of options here:

1. Go the machine-readable way and present options for the preconditions (Then, we need to discuss which ones.)
2. Specify "Precoditions" a fixed title for a vulnerability note (similar to CVE description)
3. Add a human-readable field (probably the least favorable)

[tschmidtb51]

@boschpsirt Please also formally notify about the suggestion by writing to the csaf-comment mailing list (as soon as its back online).

[tschmidtb51]

As discussed in today's TC meeting (2024-03-27):

@boschpsirt The TC tends to incorporate solution 2 into the standard. Before I set the motion to do so, any final comments?

[boschpsirt]

@tschmidtb51 we also prefer solution 2. Go for it :)

[santosomar]

The motion to accept solution 2 as suggested in #706 and include it in CSAF 2.1 has passed. No objection was received and the motion automatically passed on 2024-04-04 15:00 UTC.

This was announced at: https://groups.oasis-open.org/discussion/motion-for-706

[tschmidtb51]

@boschpsirt: The comments mailing list is now back online. Please formally announce your suggestion there, e.g. through "Please see our suggest in Github Issue XYZ (https://github.com/oasis-tcs/csaf/issues/XYZ)."

Thank you!