[ENHANCEMENT] Package Bundle .json file could follow npm SEMVER update types instead of fixed version with update rules

### Please confirm these before moving forward.

- [X] I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
- [X] This improvement refers to an existing feature. If you want to suggest a new feature, please use [this template](https://github.com/marticliment/WingetUI/issues/new?assignees=marticliment&labels=new-feature&projects=&template=feature-request.yml&title=%5BFEATURE+REQUEST%5D+%28Enter+your+description+here%29).
- [X] This improvement is not a bug. If you want to report a bug, please use [this template](https://github.com/marticliment/WingetUI/issues/new?assignees=marticliment&labels=bug&projects=&template=bug-issue.yml&title=%5BBUG%5D+%28Enter+your+description+here%29).

### Describe the improvement

Today, when exporting a package bundle we get the following
- The version installed by the bundle author: `"Version": "20.16.0"`
- The rules for the package update:
```json
"Updates": {
"UpdatesIgnored": false,
"IgnoredVersion": "20.11.1"
}
```

It raises some questions as, for example, when installing a bundle will it default for the version than check the rules? Or will it ignore the stated version and just follow the update pattern?

It would be nice to have a format similar to npm's [semantic versioning update types](https://semver.npmjs.com/#syntax-examples) where one state the type of update on the version of the package. It becomes intuitive for anyone reading or authoring the file what the intention is. I don't thing all of those option are necessary but this model seem well adopted and could be a nice improvement.

as for now, congratulation on the awesome work!! hope the best for you!

### Describe how this improvement could help users

it makes more intuitive for reading and authoring the bundle json files and can be a nice foundation for more complex update behavior if it becomes an objective of the project one day