refactor(bundler): allow downgrades, add option to disallow on Windows

[lucasfernog]

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

[JonasKruckenberg]

Sorry if I'm not up to speed on this one, but why do we need to change the default behavior? Making downgrades optional would also simplify the naming :) disallow_downgrades -> allow_downgrades and make it much easier to understand

[lucasfernog]

I feel most users would want to allow downgrades. And it's also the behavior on Linux and macOS too (AFAIK).

[FabianLars]

as far as i am concerned it's because a) we allow downgrades on macos and linux and b) it's like the main "selling point" of the server variant of the updater.

Edit: argh, too slow :))

[JonasKruckenberg]

hmmmm yeah that makes sense. What about the name though? disallow_downgrades is a nice alliteration but it's also a mouthful 😅

[amrbashir]

I think "allow_downgrades" with default value of true is better naming.

[lucasfernog]

Changed it @amrbashir @JonasKruckenberg

[JonasKruckenberg]

But isn't serde[default] for bools false?

[lucasfernog]

nice catch, thanks

[lucasfernog]

that's a problem with configuration flags that defaults to true :( way easier if it defaults to false