Add User Setting controlling Path Tokenization

[Trenly]

• I have signed the Contributor License Agreement.
• This pull request is related to an issue. Winget --version to show correct variable and / or rendered link to log #1977

Some users may not want their paths to be replaced with environment variables when displayed. This PR adds a setting to control whether the paths are tokenized or not.

---

Microsoft Reviewers: Open in CodeFlow

[yao-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Trenly]

@yao-msft - When re-running the tests locally I get similar messages for several tests. Is this the same error the pipeline is showing?

D:\Git\winget-cli\src\AppInstallerCLITests\AdminSettings.cpp(19): FAILED:
  REQUIRE( EnableAdminSetting(AdminSetting::LocalManifestFiles) )
due to unexpected exception with message:
  D:\Git\winget-cli\src\AppInstallerCommonCore\Settings.cpp(309)\
  AppInstallerCLITests.exe!00007FF708BC02DE: (caller: 00007FF708E303CB)
  Exception(1) tid(5f04) 800F024B The hash for the file is not present in the
  specified catalog file. The file is likely corrupt or the victim of
  tampering.
      [AppInstaller::Settings::`anonymous-namespace'::SecureSettingsContainer::
  Get(!verData.Found)]

[yao-msft]

The failure test case is:

SettingsAnonymizePathForDisplay/Invalid Value

with:

FAILED:
REQUIRE( userSettingTest.GetWarnings().size() == 1 )
with expansion:
2 == 1
at D:\a\1\s\src\AppInstallerCLITests\UserSettings.cpp(243)

Maybe set a breakpoint to see why 2 warnings instead of 1 warnings?

[Trenly]

The failure test case is:

SettingsAnonymizePathForDisplay/Invalid Value

with:

FAILED: REQUIRE( userSettingTest.GetWarnings().size() == 1 ) with expansion: 2 == 1 at D:\a\1\s\src\AppInstallerCLITests\UserSettings.cpp(243)

Maybe set a breakpoint to see why 2 warnings instead of 1 warnings?

It seems to be complaining about data type when I try to load the settings file. I'm taking a guess that its because the string value isn't quoted and is malformed JSON. If the latest commit doesn't fix the test, I'm not sure what the second error would be

Edit: Validated and tested locally by logging the exact errors thrown

[yao-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[yao-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[yao-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[yao-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).