Use sparkle's relaunch api for update recommend dialog

[simonhong]

User can relaunch via update recommend dialog.
Fix brave/brave-browser#2477

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:

1. Modify version in source tree to lower than released stable version for update test
   Ex, change 55.1 in package.json and chrome/VERSION.
2. Build master release mode
3. Start browser with update enabled mode and upgrade simulation mode to get update recommend dialog
   src/out/Release/Brave\ Browser.app/Contents/MacOS/Brave\ Browser --simulate-upgrade
4. Open help page and waiting to finish update and make dialog visible from app menu
5. Click relaunch button
6. Check relaunch is done

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

[simonhong]

@rebron @kjozwiak @srirambv How about uplifting this fix?
This also fixes that #1041 did.

[simonhong]

master(b166f67)
0.58.x(1616544)
0.59.x(42933cf)

[kjozwiak]

@simonhong uplift request to 0.58.x approved after deliberating with @srirambv & @rebron 👍Typically, you should merge the PR into master & dev before requesting beta approval.

Please add/remove all needed labels and ensure that the associated issue is in the correct milestone.