Prevent high request load after notification

First and foremost, thanks for having created this project! It's greatly helping our instance's runtime.

I'd like to focus on a particularly nasty side-effect of the reaction to a notification, when there are many clients (>20) and big folders in sync:

1. A client updates a file / folder;
2. A push notification is sent to all connected NC clients;
3. Immediately after, all clients issue a number of PROPFIND requests to get more info and decide what to do;
4. The server load easily spikes to 80-95% of all available cores;
5. Just a few seconds after the first push, another user changes a different file/folder;
6. go to number 2.

The above is going to pile up easily and use up all the available cores when many users are working on a big share.
As a result of that, on a user perspective the clients tend to stay in "synchronizing" state for most of the time and appear very slowly responsive, even if only few small changes really happened in the shares.

A solution to highly mitigate the above side effects would be to:

• Add more information to the push notification message so that the clients don't always need to ask back additional info
• Change the NC client push notification code to make use of the additional info and avoid issuing a bunch of requests.

Hope this helps, thanks!

Start by tracing the push notification payload and the client reaction that triggers follow-up PROPFIND requests; the issue does not name specific files or tests. Define the additional information and update both server and client behavior so notifications avoid unnecessary requests and the resulting load spike is reduced.