Add setting for installer log file names

[Trenly]

• I have signed the Contributor License Agreement.
• I have updated the Release Notes.
  • Waiting for bump of version to 1.28
• This pull request is related to an issue.
  • Related to Running into Windows path length limits for installer log files #2036

Sometimes the Manifest name is just too long. While I would love to be able to give users the ability to control the format directly using token replacement and all sorts of other cool stuff, that's a bit much for right now.

To help alleviate the issue, I've added a setting that controls how installer file names are generated. With this change, instead of being forced into the Package ID and version with timestamp, it is now possible to have the default installer log name be shorter. While this doesn't actually resolve the issue, it does make it possible to at least mitigate

• Manifest - Default, matches current behavior
• Timestamp - Includes just the timestamp as the installer log name
• GUID - Creates a new GUID and uses that as the installer log name
• ShortGuid - Creates a new GUID and uses the first 8 characters as the installer log name

Note that this only affects the installer log name, not the WinGet log name, and only for installers which support passing of the log name. This PR does not affect the behavior of --log <location>

---

Microsoft Reviewers: Open in CodeFlow

[Trenly]

Marking as draft to fix merge conflicts

[Trenly]

Finally got around to fixing the merge conflicts.

Interesting note, if this gets merged, it will push the repo over 1000 unit tests :D

===============================================================================
All tests passed (28169 assertions in 1000 test cases)

[JohnMcPMS]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).