Get-WinGetSettings should write a structured object in PowerShell

Description of the new feature / enhancement

In the PowerShell module, Get-WingetSettings writes a generic hashtable to the pipeline. This requires the user to jump through hoops to see the actual settings. The command should write a structured object to the pipeline.

Proposed technical implementation details

Here's a helper script I wrote as a demonstration to convert the command output to something more meaningful.

$ws = Get-WingetSettings
$out = @{
    PSTypeName = "winget.client.settings"
    UserSettingsFile = $ws.userSettingsFile
}
$ws.adminSettings.GetEnumerator() | ForEach-Object {$out.Add($_.Key,$_.value)}
new-object -TypeName PSObject -Property $out

I now get a more user-friendly object.

LocalManifestFiles                        : False
LocalArchiveMalwareScanOverride           : False
UserSettingsFile                          : C:\Users\Jeff\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d
                                            8bbwe\LocalState\settings.json
InstallerHashOverride                     : False
BypassCertificatePinningForMicrosoftStore : False

My example is inserting a type name in the event I want to create a format extension. You have the information. It just needs to be presented in a better format.

Start by locating the PowerShell module implementation of Get-WingetSettings and compare its current pipeline output with the structured-object example in the issue. Done means the command directly emits a user-friendly structured object exposing the user settings file and administrative settings without conversion hoops.