[New Feature]: Enable-WingetSetting and Disable-WingetSetting should return confirmation

Description of the new feature/enhancement

Currently, running Enable-WingetSetting LocalManifestFiles or Disable-WingetSetting LocalManifestFiles provides no output and it is not clear whether the command succeeded or not. The native commands winget settings --<Enable|Disable> LocalManifestFiles provide output that the setting was either enabled or disabled, It would provide much better feedback to the user if the PowerShell module returned the setting and its state as a confirmation that it was set

Proposed technical implementation details (optional)

PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs> Enable-WingetSetting LocalManifestFiles
Name               Value
----               -----
LocalManifestFiles True

PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs>
PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs> Disable-WingetSetting LocalManifestFiles
Name               Value
----               -----
LocalManifestFiles False

Start with the implementations of Enable-WingetSetting and Disable-WingetSetting, then trace how each command currently handles its setting change. The work is done when both commands report the setting name and its resulting true or false state as shown in the issue.