Altering group membership has performance impact on large instances

Issue Summary

This issue comes from JFR data from JAC.
Every time we change group membership, nodes in the cluster recalculate the current user count to check against the license. This process is asynchronous and deduplicated, but I believe it needs to be further improved.
For JAC, I've seen it triggered 375 time in a timespan of 4 hours, with each call taking ~20s (that's a 2h total).
It has been a problem in the past and is currently invisible in our synthetic testing.

Steps to Reproduce

1. Set up a breakpoint in com.atlassian.jira.application.DefaultApplicationRoleManager#clearUserCounts
2. add a user to the system

Expected Results

1. the method will not execute the recalc right away
2. the method will not be called on all the nodes

Actual Results

1. the recalc is initiated right away
2. each node recalculates data individually

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available