Azure DevOps CI

[villagra]

Changes made:

• Generate appx bundle for all platforms: It doesn't affect the download size, the store client will download just the bits required for each platform and having all is no extra effort and will perform much better being native for the platform, specially ARM|ARM64. Do not remove them.
• Build just in Release config. It doesn't make sense to build in debug. Building in release will also generate test packages that can be sideloaded (folder Jellyfin_x.x.x_test)
• Added step to publish packages in the drop folder. Notes:
• Do not rename the Jellyfin_TemporaryKey.pfx file. This is the name used in vs and the process to generate test certificates will always use that name.
• There is no autoincrement with each build, what I usually do it generate packages based in the number of commits. If you want to follow that approach, the mayor and minor will be automatically configured and the build will be the number of commits, something like: Jellyfin_1.1.3234

[EraYaN]

* There is no autoincrement with each build, what I usually do it generate packages based in the number of commits. If you want to follow that approach, the mayor and minor will be automatically configured and the build will be the number of commits, something like: Jellyfin_1.1.3234

The number of commits can change and is not strictly increasing, so we should probably try to stick to regular semver if at all possible. If you want to add something unique you can add the git hash to the InformationalVersion.

[dkanada]

I think incrementing manually with semver would be fine on its own.