[DDW-1061] Downloaded installer being left behind after wallet is updated to latest version

[shawnbusuttil]

This PR intends to fix the problem where we have downloaded installers being left behind after Daedalus is updated.

Screenshots

No UI changes.

Local Testing Steps:

1. Change package.json to 4.8.0.
2. Run the local environment.
3. Wait for the download to finish. You don't have to go through the installation as it will just install the Testnet without the updated logic.
4. Make sure you have the finished installer in the Daedalus Testnet state directory downloads folder.
5. Stop the environment.
6. Change package.json to 4.9.0.
7. Run the local environment.
8. Open the downloads folder in state directory. The installer shouldn't be there anymore.

Testing Checklist

• Slack QA thread
• Test

---

Review Checklist

Basics

• PR assigned to the PR author(s)
• input-output-hk/daedalus-dev and input-output-hk/daedalus-qa assigned as PR reviewers
• If there are UI changes, Alexander Rukin assigned as an additional reviewer
• All visual regression testing has been reviewed (assign run Chromatic label to PR to trigger the run)
• PR has appropriate labels (release-vNext, feature/bug/chore, WIP)
• PR link is added to a Jira ticket, ticket moved to In Review
• PR is updated to the most recent version of the target branch (and there are no conflicts)
• PR has a good description that summarizes all changes
• PR contains screenshots (in case of UI changes)
• CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
• There are no missing translations (running yarn manage:translations produces no changes)
• Text changes are proofread and approved (Jane Wild / Amy Reeve)
• Japanese text changes are proofread and approved (Junko Oda)
• Storybook works and no stories are broken (yarn storybook)
• In case of dependency changes yarn.lock file is updated

Code Quality

• Important parts of the code are properly commented and documented
• Code is properly typed with typescript types
• React components are split-up enough to avoid unnecessary re-renderings
• Any code that only works in main process is neatly separated from components

Testing

• New feature/change is covered by acceptance tests
• New feature/change is manually tested and approved by QA team
• All existing acceptance tests are still up-to-date
• New feature/change is covered by Daedalus Testing scenario
• All existing Daedalus Testing scenarios are still up-to-date

After Review

• Update Slack QA thread by marking it with a green checkmark

[danielmain]

Tested successfully using tweaks and a special build. So @daedalus-qa you don't need to test it.

[danielmain]

@shawnbusuttil great Job. Tested and created a video

[shawnbusuttil]

@shawnbusuttil great Job. Tested and created a video

Thank you for your help! 😃

[danielmain]

Tested on MacOs

mac.mp4

[danielmain]

Tested on Windows 11 cc: @input-output-hk/daedalus-qa

win.mp4