Audit and split requirements combining multiple obligations

As per the style guide:

A Single Requirement corresponds to a single Test
Every requirement MUST describe exactly one testable behavior. Each requirement should map directly to a single implementation test. If a requirement has multiple obligations that can pass/fail independently, split them into separate requirements. An easy way to enforce this is to avoid using "and" in the requirement text.

Several requirements currently join two or more independently-testable obligations with "and" (e.g., "evaluated ... and blocked", "document when and how"). A project could satisfy one clause while failing the other, so these need to be reviewed and, where applicable, split so each requirement maps to a single test.

Precedent: #443 split BR-01 into three requirements.

Requirements to review

• OSPS-VM-06.02
• OSPS-VM-05.03
• OSPS-VM-05.01
• OSPS-VM-01.01
• OSPS-QA-06.02

CC: @eddie-knight @funnelfiasco

Start with docs/style-guide.md, then locate the source definitions for OSPS-VM-06.02, OSPS-VM-05.03, OSPS-VM-05.01, OSPS-VM-01.01, and OSPS-QA-06.02. Compare each requirement with the single-test rule and precedent in #443. Done means every independently testable obligation is represented by its own requirement.