Create and upload silent and untagged Windows Omaha installers

[mbacchi]

Fixes: brave/brave-browser#2210

Submitter Checklist:

• Submitted a ticket for my issue if one did not already exist.
• Used Github auto-closing keywords in the commit message.
• Added/updated tests for this change (for new code or code which already has tests).
• Verified that these changes build without errors on
  • Windows
  • macOS
  • Linux
• Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests) on
  • Windows
  • macOS
  • Linux
• Ran git rebase master (if needed).
• Ran git rebase -i to squash commits (if needed).
• Tagged reviewers and labelled the pull request as needed.
• Request a security/privacy review as needed.
• Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone

Test Plan:

Reviewer Checklist:

• New files have MPL-2.0 license header.
• Request a security/privacy review as needed.
• Adequate test coverage exists to prevent regressions
• Verify test plan is specified in PR before merging to source

[kjozwiak]

Approving for uplift to 0.57.x after deliberating with @srirambv & @rebron 👍

@mbacchi before tagging issues as uplift-request/0.57.x-Beta, they should usually:

• have passed review, closed and merged into master
• merged into dev

Once merged into dev, request for approval 👍

[mihaiplesa]

looks good

[mihaiplesa]

let's merge

[mbacchi]

Thanks @kjozwiak I'll remember that process for the next time. Appreciate your explanation.

[mbacchi]

master: e3491ee
0.58.x: e9088ff
0.57.x: d59f4e4

[bbondy]

adding merged label.