Fix default revision number assigned to packages

[Tostti]

Description

The current package generation methods assign the application’s build number to the package’s revision number. This build number is utilized in URLs to access resources within the application.
This can cause caching issues when packages share the same revision number but are from different versions.

To solve this, we will modify the package generation scripts to use the previous build convention (5 digits: 3 for the version and 2 for the revision. e.g., 49001). This approach will link the number to both the version and revision and thus will prevent the aforementioned issue.