Add default installer precedence if not defined by user

[Trenly]

• I have signed the Contributor License Agreement.
• I have updated the Release Notes.
• This pull request is related to an issue.
  • Ability to specify a default installer type in the manifest #3866 (addresses comment, does not resolve core issue)

This PR adds a default order of precedence for installer types if the user has not specified one. This ensures that ordering in a manifest is less important. While this has the potential to cause some upset with publishers who would prefer a different default order, the linked issue can remain open for tracking those requests.

Future work could involve merging the default preferences with user preferences so that any installer types the user has not specified as their preference still adhere to this default ordering, but I presumed that to be out of scope for this feature

---

Microsoft Reviewers: Open in CodeFlow

[Trenly]

@jsoref - I'm not sure I understand why this error is coming up, when it didn't come up on PRs from a few days ago and nothing has changed in the workflow file. Any advice?

[jsoref]

• This is tracked as False-positive "Unsafe Permissions" (exit 5) on fork PRs - GitHub API now returns 422 instead of 403 check-spelling/check-spelling#103 -- I've developed a fix based on this report and will try to release a version shortly.

Unfortunately the only choices are updating to the prerelease version (pinned by sha) or adding a guard that skips check-spelling for PRs where the base repo doesn't match the head repo (the check only applies in that case).

[JohnMcPMS]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).