fix: Shipped apps should include the Nextcloud version in the cache buster

[susnux]

• Resolves: [Bug]: Force reload required after upgrade 29 -> 30  #46976

Summary

1. The hash should also include the Nextcloud version if the app is shipped as every new Nextcloud update = new app version
2. Cache the hash to prevent re-generation if the path is the same (e.g. the same app uses a lot of scripts / styles).

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[susnux]

/backport to stable30

[backportbot]

The backport to stable30 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable30
git pull origin stable30

# Create the new backport branch
git checkout -b backport/48650/stable30

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 980ab1f5

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/48650/stable30

Error: Failed to push branch backport/48650/stable30: fatal: could not read Username for 'https://github.com': No such device or address

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.