Update SCBs match updates through the CB approval process (Marlin)

[ahuynhMITRE]

🗣 Description

As the Marlin SCBs undergo the CB approval process this PR will be updated to reflect all of the consolidated SCB updates.

💭 Motivation and context

This work is required to process and publish the v1.6.0 (Marlin) release for the SCBs.
Closes #1661
Closes PR #1679

🧪 Testing

N/A SCB changes

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• PR targets the correct parent branch (e.g., main or release-name) for merge.
• Changes are limited to a single goal - eschew scope creep!
• Changes are sized such that they do not touch excessive number of files.
• All future TODOs are captured in issues, which are referenced in code comments.
• All relevant type-of-change labels added.
• All relevant project fields are set.
• All relevant repo and/or project documentation updated to reflect these changes.
• Unit tests added/updated to cover PowerShell and Rego changes.
• Functional tests added/updated to cover PowerShell and Rego changes.
• All relevant functional tests passed.
• All automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ Pre-merge checklist

• PR passed smoke test check.

• Feature branch has been rebased against changes from parent branch, as needed

  Use Rebase branch button below or use this reference to rebase from the command line.

• Resolved all merge conflicts on branch

• Notified merge coordinator that PR is ready for merge via comment mention

• Demonstrate changes to the team for questions and comments.
  (Note: Only required for issues of size Medium or larger)

✅ Post-merge checklist

• Feature branch deleted after merge to clean up repository.
• Verified that all checks pass on parent branch (e.g., main or release-name) after merge.

[ahuynhMITRE]

@mitchelbaker-cisa added small updates from the section leads reviews, still awiting JCDC, OCC and front office reivews