Create Json Output

[adhilto]

🗣 Description

Create a single json file (defaults to ScubaResults.json) that contains all of the ScubaGear output, including:

• Metadata (date, tenant details, ScubaGear module version)
• Json version of the html reports
• Raw provider output

💭 Motivation and context

Closes #913.

🧪 Testing

• Tested via Invoke-Scuba
• Tested via Invoke-RunCached
• Modified pester test cases

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

Looks good - two observations:

1. The individual 'json' reports appear to be not needed - is it useful to clean them up.
2. The defining of a function so it can be found to mock suggestion is optional. I have been changing them as I revisit tests.

[adhilto]

1. The individual 'json' reports appear to be not needed - is it useful to clean them up.

David had a similar suggestion, so I will make that change.

He also recommended I add a switch to keep the size of the output down. If true, create the ScubaResults.json file and delete the redundant files (the individual jsons you mentioned and the provider output). If false, don't create ScubaResults.json, just execute as normal.

Unless you have any objections, I'll go ahead and make both changes.

[crutchfield]

1. The individual 'json' reports appear to be not needed - is it useful to clean them up.

David had a similar suggestion, so I will make that change.

He also recommended I add a switch to keep the size of the output down. If true, create the ScubaResults.json file and delete the redundant files (the individual jsons you mentioned and the provider output). If false, don't create ScubaResults.json, just execute as normal.

Unless you have any objections, I'll go ahead and make both changes.

Sounds good to me

[buidav]

Looks good, however have one last comment.

[adhilto]

@nanda-katikaneni this PR is ready