Refactor escape sequence handling

[adhilto]

🗣 Description

This PR makes it so that ScubaGear no longer attempts to remove all backslashes, only the specific character sequences known to cause problems for Rego.

💭 Motivation and context

The provider output can include characters that Rego attempts to interpret as escape sequences (such as \/, which is output when you convert a date to json in PowerShell 5 (e.g., Get-Date | Convert-ToJson). These sequences result in the error "unable to parse input: yaml: line x: found unknown escape character." Previously, ScubaGear attempted to circumvent this issue by wholesale removing all backslashes from the resulting json. However, there are cases where that technique resulted in broken json (see #807 and #770).

Closes #818.

🧪 Testing

Tested on the E5, G3, G5, and GCCHigh tenants, asserting that the number of tests passing/failing matched for both this branch and main. Also, engineered a problematic transport rule that would cause a parsing error as described in #807 (comment). That rule causes the parsing error in main but not this branch.

✅ 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.
• These code changes follow the ScubaGear content style guide.
• 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.
• 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

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

[crutchfield]

Ran Scuba against all products and review reports. Verified ProviderSettingExport has no back slashes.

[schrolla]

Just had one question about the update to escaping based on the Date example. See below.

[schrolla]

Changes look good and all testing works as expected.

[adhilto]

@nanda-katikaneni this PR is ready to go.