feat: Add import/export device settings utils for PS5

[tustanivsky]

This PR adds two new public functions (Export-DeviceSettings and Import-DeviceSettings) that expose the prospero-ctrl settings export and settings import commands for connected PlayStation 5 devkits.

Key changes:

• Add settingsimport command to PlayStation5Provider
• Add ExportSettings() and ImportSettings() methods to the base DeviceProvider class
• Add Export-DeviceSettings and Import-DeviceSettings public functions
• Register both functions in the module manifest

Related items:

• https://github.com/getsentry/sentry-playstation/pull/104

#skip-changelog

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Duplicate settings export logic bypasses new wrapper
  • Replaced direct InvokeCommand('settingsexport') call with ExportSettings() method in PlayStation5Provider.GetDiagnostics().

Or push these changes by commenting:

@cursor push 844694767a

Preview (844694767a)

diff --git a/app-runner/Private/DeviceProviders/PlayStation5Provider.ps1 b/app-runner/Private/DeviceProviders/PlayStation5Provider.ps1
--- a/app-runner/Private/DeviceProviders/PlayStation5Provider.ps1
+++ b/app-runner/Private/DeviceProviders/PlayStation5Provider.ps1
@@ -191,7 +191,7 @@
         # Run prospero-ctrl settings export
         try {
             $settingsFile = Join-Path $OutputDirectory "$datePrefix-settings.xml"
-            $this.InvokeCommand('settingsexport', @($settingsFile))
+            $this.ExportSettings($settingsFile)
             $results.Files += $settingsFile
             Write-Debug "Settings exported to: $settingsFile"
         } catch {

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

[cursor]

Duplicate settings export logic bypasses new wrapper

Low Severity

The PlayStation5Provider.GetDiagnostics() method directly calls $this.InvokeCommand('settingsexport', @($settingsFile)) instead of using the newly introduced $this.ExportSettings($settingsFile) method. This PR introduced ExportSettings to centralize this logic, but the existing inline call in GetDiagnostics was not updated, leaving two parallel code paths for the same operation. Any future changes made to ExportSettings (e.g., validation, pre/post-processing) won't automatically apply to the diagnostics export path.

Additional Locations (1)

• app-runner/Private/DeviceProviders/DeviceProvider.ps1#L556-L560