Add UUID to JSON output

[adhilto]

🗣 Description

Add UUID to the JSON output (both raw provider output and ScubaResults.json).

💭 Motivation and context

Closes #1336.

🧪 Testing

I performed the following tests:

1. Invoke-Scuba. Worked as expected.
2. Invoke-Scuba -KeepIndividualJson. Worked as expected.
3. Invoke-ScubaCached -ExportProvider $false with input generated without the KeepIndividualJson flag. Worked as expected.
4. Invoke-ScubaCached -ExportProvider $false with input generated with the KeepIndividualJson flag. Worked as expected. (assuming you manually fix Bug with Invoke-SCuBACached if no provider json #1329 as Fix functional testing and cached output errors #1334 hasn't been merged yet).
5. Invoke-ScubaCached -KeepIndividualJson -ExportProvider $false with input generated without the KeepIndividualJson flag. Worked as expected.
6. Invoke-ScubaCached -KeepIndividualJson -ExportProvider $false with input generated with the KeepIndividualJson flag.
7. Invoke-ScubaCached -ExportProvider $false with input generated without the KeepIndividualJson flag and without the "report_uuid" field (to ensure backwards compatibility with output created before this PR). Worked as expected.
8. Invoke-ScubaCached -ExportProvider $false with input generated with the KeepIndividualJson flag and without the "report_uuid" field. Worked as expected.
9. Invoke-SCuBACached. Worked as expected.
10. Invoke-SCuBACached -KeepIndividualJson. Worked as expected.

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

[schrolla]

Running through the testing section, all tests worked as expected. However, I did have some thoughts about ordering for the new report_uuid field for readability purposes and a bit more error handling and unit testing around New-Guid.

Would a future TODO be to also add this report UUID somewhere in the HTML report as well so that the two reports (JSON and HTML) could be correlated? Also, so multiple HTML report runs could be disambiguated (other than using the timestamp).

[schrolla]

Reviewed newest updates which addressed previous comments. Ran unit tests which passed and ran several variations of Invoke-Scuba and Invoke-ScubaCached which worked as well. Looks good.

[adhilto]

@nanda-katikaneni ready to be merged. The failed smoke tests all appear to be due to the Power Platform issue #1345.