Update SCB acronym to read as "Secure Configuration Baseline" throughout repo

[ahuynhMITRE]

🗣 Description

We have been referencing SCB as both "Security Configuration Baseline" and "Secure Configuration Baseline". This PR and accompanying issue addresses the inconsistency and updates all references to "Secure Configuration Baseline" to match BOD language.

💭 Motivation and context

Change is required to have the acronym of SCB to be consistently referred as "Secure Configuration Baseline" matching the BOD language. Using a the replace functionality this has been done throughout the repo.

Closes #1432

🧪 Testing

Check throughout the repo that "Security Configuration Baseline" instances have been replaced with "Secure Configuration Baseline".

✅ 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.
• Related issues these changes resolve are linked preferably via closing keywords.
• 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.
• 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

✅ 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.