Content Permission changes are propagated between nodes one at a time, should be in bulk

When updating the content permissions on a page with many descendants, Confluence will generate a large number of events that it will send to the other nodes in the cluster one at a time. Confluence should batch these operations up so that the changes can be made in bulk on each node instead.