🗣 Description

Modified the PSSA config file so that it checks for the presence of help comments for PowerShell functions. It does not check for validity or formatting (as per https://learn.microsoft.com/en-us/powershell/utility-modules/psscriptanalyzer/rules/providecommenthelp?view=ps-modules).

Note: This check is considered to be of severity "information", so this problem does not currently cause the pipelines to fail.

💭 Motivation and context

Closes: #1489

🧪 Testing

Ran the CI and workflow pipelines.
Example of the results (with 148 missing help comments): https://github.com/cisagov/ScubaGear/actions/runs/12485122722/job/34843478350

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

See #1491

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