integrate safety impact changes into documentation

[j---]

While resolving #311 in code, #439 focused (appropriately narrowly) on the decision point definitions in the python.

ADH noted there that

Also, I am avoiding updating any additional documentation, including CSV files and trees. Decision models that include any of the safety decision points should be updated eventually, but again that seems like it could make this PR too big if we tried to tackle it all at once. My suggestion is that we leave a separate issue behind to update the safety-dependent decision models to reflect the new versions.

This issue will be resolved when the following locations update the necessary safety impact details:

• CSV files
• Example decision trees
• Decision models using safety decision points
• CVSS v4 updates include note that this new version of safety impact aligns with the CVSS v4 supplemental metric safety (still to do for Add CVSS v4 crosswalk documentation #318, may be resolved as part of that issue)

These tasks are distinct from #380 and can be resolved independently of that issue.

[ahouseholder]

• Revise Safety decision point value text #482 might soft-block or at least influence resolution of this issue