Fix: force refresh of remote tree on precalculation and replace relative with the custom relative on create backup upload executor

[AlexisMora]

What is Changed / Added

create-backup-upload-executor.ts: Changed the relative import from node:path to the project's custom relative utility apps/backups/utils/relative. Node's relative produces paths without a leading / for example sub1/file.txt, while the RemoteTree keys folders with a leading / for example: /sub1. This mismatch caused remoteTree.getParent() to throw when looking up parent folders for file uploads, silently aborting the async queue.

precalculate-backup-item-count.ts: Added forceRefresh: true to the remoteTreeBuilder.run() call so the remote tree is always fetched fresh before precalculating item counts.

---

Why

The original sequential upload code used the custom relative utility, but the new create-backup-upload-executor.ts imported relative from node:path. This caused backups of folders with subfolders to create the folder structure correctly but skip all file uploads and making the parent lookup failed because sub1 != /sub1, the error was unhandled inside the async queue, and the queue silently stopped processing.

The forceRefresh change ensures that repeated manual backups always diff against the latest remote state, preventing stale tree data from causing unnecessary 409 conflicts or incorrect diff calculations.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud