fix(files): report new files as new in the files:scan summary

[seenickcode]

Summary

occ files:scan has reported every new file as "Updated" (never "New")
since the summary table was introduced in 292c0e5.

Root cause: the addToCache listener decides between NodeAddedToCache and
FileCacheUpdated by checking if ($fileId), but Cache\Scanner emits
$fileId = -1 for newly inserted entries, which is truthy. As a result,
the NodeAddedToCache branch was unreachable.

What it does

• Checks for the actual -1 sentinel instead, so newly inserted entries
  dispatch NodeAddedToCache and existing entries dispatch
  FileCacheUpdated
• Adds a regression test asserting that a first scan dispatches
  NodeAddedToCache and a re-scan of a modified file dispatches
  FileCacheUpdated

How I verified

Setup: Nextcloud master, MariaDB, an S3 (MinIO) external storage mount with
100 files in 35 folders, mounted at /legacy for user demo01.

Before each scan I cleared the mount's rows from the file cache so every
entry the scan finds is guaranteed new:

DELETE FROM oc_filecache WHERE storage = <numeric_id of the mount>;

On master — all 135 entries were just deleted, so all of them are new,
yet the summary reports none:

$ occ files:scan demo01 --path=/demo01/files/legacy
Starting scan for user 1 out of 1 (demo01)
+---------+-------+-----+---------+---------+--------+--------------+
| Folders | Files | New | Updated | Removed | Errors | Elapsed time |
+---------+-------+-----+---------+---------+--------+--------------+
| 35      | 100   | 0   | 135     | 0       | 0      | 00:00:00     |
+---------+-------+-----+---------+---------+--------+--------------+

On this branch — identical steps:

$ occ files:scan demo01 --path=/demo01/files/legacy
Starting scan for user 1 out of 1 (demo01)
+---------+-------+-----+---------+---------+--------+--------------+
| Folders | Files | New | Updated | Removed | Errors | Elapsed time |
+---------+-------+-----+---------+---------+--------+--------------+
| 35      | 100   | 135 | 0       | 0       | 0      | 00:00:00     |
+---------+-------+-----+---------+---------+--------+--------------+

The included regression test also fails against master and passes with the
fix (first scan must dispatch NodeAddedToCache, re-scan of a modified
file must dispatch FileCacheUpdated).

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)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI

[seenickcode]

SGTM

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)