fix(core/tauri): upgrade open to 3.2 to fix a bug on Windows

[thep0y]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
• I have added a convincing reason for adding this feature, if necessary

Other information

For specific bug details, please refer to https://github.com/Byron/open-rs/releases/tag/v4.0.0

[FabianLars]

Thanks for contributing! Unfortunately we can't merge this into the dev branch because of the MSRV bum to 1.62. We're stuck with 1.59 for dependencies that are also used on Linux :/ See the conversation here: #6332 - if we change the approach in that PR, we'll also change it for this dependency if we bump it all the way up to 1.62

p.s. upgrading dependencies is handled by the renovate bot :)

[thep0y]

Downgrading open to 3.2.0 can also fix this bug, 3.2.0 can run on 1.59.

[FabianLars]

Tauri should already use 3.2 - we didn't lock it so cargo update in user's project should update it to the latest 3.x release.

[FabianLars]

3.4 is kinda buggy (more than 3.2 lol), so unpinning 3.2 makes this PR useless @lucasfernog

[lucasfernog]

IIRC 3.4 was yanked? I'm on my phone lol @FabianLars

[FabianLars]

ah you're right, nvm then ✌️