Save parameters to json file

[aormu]

🗣 Description

Save ScubaGoggles Parameters/config to JSON output.

Save configuration to a JSON file.

💭 Motivation and context

This enables users to review the parameters utilized to operate this tool in the future.

Save the parameters value in a JSON file.

Closes #440

🧪 Testing

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• If applicable, All future TODOs are captured in issues, which are referenced in the PR description.
• The relevant issues PR resolves are linked preferably via closing keywords.
• All relevant type-of-change labels have been added.
• I have read and agree to the CONTRIBUTING.md document.
• These code changes follow cisagov code standards.
• All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
• Tests have been added and/or modified to cover the changes in this PR.
• All new and existing tests pass.

✅ Pre-merge Checklist

• This PR has been smoke tested to ensure main is in a functional state when this PR is merged.
• Squash all commits into one PR level commit using the Squash and merge button.

✅ Post-merge Checklist

• Delete the branch to clean up.
• Close issues resolved by this PR if the closing keywords did not activate.

[adhilto]

A few things:

1. Sorry this wasn't detailed in the issued, but for consistency with ScubaGear, the parameters shouldn't be saved as a separate json file. They should be saved in the primary ScubaResults.json file, in the Raw section, under the sub-key scuba_config.
2. The Pylinter is reporting several issues that should be resolved before merging: https://github.com/cisagov/ScubaGoggles/actions/runs/11691841759/job/32559891620?pr=551
3. There are several merge conflicts. I know @rlxdev offered to help with any merge conflicts, you might ask him for help if you need it. I'm happy to help as well.
4. Please describe what testing you performed in the "Testing" section of the pull request description.

[buidav]

A few things:

1. Sorry this wasn't detailed in the issued, but for consistency with ScubaGear, the parameters shouldn't be saved as a separate json file. They should be saved in the primary ScubaResults.json file, in the `Raw` section, under the sub-key `scuba_config`.

2. The Pylinter is reporting several issues that should be resolved before merging: https://github.com/cisagov/ScubaGoggles/actions/runs/11691841759/job/32559891620?pr=551

3. There are several merge conflicts. I know @rlxdev offered to help with any merge conflicts, you might ask him for help if you need it. I'm happy to help as well.

4. Please describe what testing you performed in the "Testing" section of the pull request description.

@aormu Alden's comments still need to be addressed.
Also why is this branch pointing towards merging into 519-policy-api-updates instead of main?