Correct the location argument to Set-Utf8NoBom in Invoke-ScubaCached

[buidav]

🗣 Description

• Provide the correct location argument to Set-Utf8NoBom in Invoke-SCuBACached
• Days since David has put a bug in the functional tests: 0

💭 Motivation and context

Closes #1329

🧪 Testing

• From adhilto

1. Create output with merged json. From the latest on main, this is as easy as Invoke-Scuba
2. Invoke-ScubaCached -OutPath .\path-to-output-folder-from-step-1\ -ExportProvider $false

• Reran functional tests. Particularly Defender and AAD which make heavy use of this specific function.
• Failing functional tests seem to be related to Functional tests for Defender cannot find AADReport.json #1328 and FunctionalTestUtils LoadProviderExport loads incorrect file #1333

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

[schrolla]

@buidav So I think I actually need this fix as well to get a clean run with #1333. Would it make sense to kill one or the other of our PRs and put both fixes in one since we won't get a clean functional test run unless both fixes are present?

[buidav]

Closing as fix will be merged in #1334