Preserve Configuration Editor filters across product tabs and scope policy totals per product

[DickTracyII]

🗣 Description

This change updates the Configuration Editor filtering behavior so that the selected filter (e.g., “Configured Only”) is preserved when switching between product tabs/configuration type tabs, instead of resetting unexpectedly. It also corrects the policy total counter so totals reflect the currently selected product(s) context rather than an aggregate count across all products.

This update also restores standard window chrome (title bar controls) and ensures the window can be moved and resized correctly, including on smaller laptop displays (13/15 inch) where the title bar and controls were previously missing.

This change introduces a ScubaGear baseline viewer app that lets users quickly browse SCuBA baselines from the baselines packaged with the module, rather than pulling “live” baselines at runtime. The goal is fast, predictable baseline viewing that matches the installed module version and avoids confusion about data source/version

Resolves: #1868
Resolves: #1875

💭 Motivation and context

Users navigating by “Configured” across multiple products expect the same filter to remain applied unless they intentionally change it. Previously, switching tabs reset the filter and showed totals across all products (e.g., Omit Policies showing totals not scoped to the selected product), which made it hard to compare “Configured Only” items across products.

Why ScubaGear baseline viewer app is required / what problem it solves:

Users need a quick way to review baselines locally without relying on “live” baselines that have changed and don't reflect release baselines. Viewing baselines from the module improves consistency: what the user sees aligns to the version they’re running, which reduces ambiguity about baseline provenance and timing.

🧪 Testing

Environment:

• Windows 11
• Windows PowerShell 5.1
• ScubaGear version: 1.7.0+

Manual verification:

1. Run Start-SCuBAConfigApp
   2, Confirm Window comes up but other windows can go in front of it.
2. Check more than one Product (eg. AAD, EXO)
3. Go to Exclusions
4. Select AAD
5. Set the filter from All Configurations to Configured Only
6. Switch to another product (e.g., EXO)
7. Confirm:
   • The filter remains Configured Only
   • The policy total counter reflects the checked product context (not an all-products aggregate)
8. Repeat switching across multiple product tabs to confirm persistence is consistent.

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