Consider events specific to license grant and revoke

I'm actually not sure if this would be better than existing events emitted based on license updates and / or state transitions. At present, we do not have the ability to react explicitly to license granting or revocation, even though there are potentially multiple places where that might happen, complicating relying on other transitions.

The question is ... if we implement use case specific events, should we try to do something different, like ensure the event is emitted after the save that triggered the initial grant or revoke has been completed?