Add the report UUID to the ScubaResults.json filename

[adhilto]

🗣 Description

Add the report UUID to the ScubaResults.json filename.

💭 Motivation and context

Ensures each results file has a unique file name. Closes #1422.

🧪 Testing

• Ensured PowerShell unit tests pass
• Added new unit tests to cover the case when there are multiple matching ScubaResults*.json files
• Manually tested Invoke-Scuba, works as expected
• Manually tested Invoke-ScubaCached, works as expected
• Manually tested Invoke-ScubaCached where the input folder has one file matching "ScubaResults*.json", "ScubaResults.json", works as expected
• Manually tested Invoke-ScubaCached where the input folder has one file matching "ScubaResults*.json", "ScubaResults_{uuid}.json", works as expected
• Manually tested Invoke-ScubaCached where the input folder has two file matching "ScubaResults*.json", the most recently created file is used, as expected
• Manually tested Invoke-Scuba and Invoke-ScubaCached with a non-default OutPath parameter
• Manually tested both Invoke-Scuba and Invoke-ScubaCached with a non-default OutJsonFileName parameter

✅ 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

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