The cache of the Cache macro should be invalidated when it's modified

It's a pain right now to modify the content of a cache macro if that macro has a long timetolive configuration.

At least we could invalidate it when the document is modified.

Knowing that the macro itself has been modified is a bit more complex but we could do it in a second step.