when "test quota on write" fails, it should notify pod owner

In catching up on a lot of discussion and updates, it seems that when the "test quota on write" fails it results in a notification to the attempting writer -- so if @kjetilk tries to write to @RubenVerborgh's INBOX and that write would exhaust quota, @kjetilk gets notified -- but @RubenVerborgh does not.

This is troublesome, as @kjetilk's best (and possibly only) way to inform @RubenVerborgh of this problem is via his inbox ... which is full. I think that this is a place where NSS might use @RubenVerborgh's email address to send such a notification without consuming further NSS-quota.

Originally posted in https://github.com/solid/node-solid-server/issues/918#issuecomment-450062727

Commencez par localiser l’implémentation Node.js de l’échec « test quota on write » et le chemin de notification, puis lisez la discussion de l’issue 918 liée pour en comprendre le contexte. Le travail est terminé lorsque le propriétaire du pod est informé de l’échec de quota sans consommer de quota supplémentaire, tandis que le comportement de notification existant du writer reste compris et couvert.