BucketEventsListener post-connect state mismatches

While adding / testing for MB-58897, it was discovered that the internal state of BucketEventsListener does not remain consistent through several events, at least in the case where multiple links are sharing the same BucketEventsListener instance (i.e. aggregated links):

• dropping datasets
• dropping analytics scopes
• collections created on new analytics scopes, on already connected buckets

In these cases, the "buckets" and "linkrefs" within the BucketEventsListener remains as it was at connect time, and is not properly maintained. As this lifecycle is difficult to get right, it is not appropriate to try to address in a maintenance release (e.g. 7.2.3). Given the customer escalations we've seen around these lifecycle issues, we need to take the time to get this right for 7.2.4.

These and all other conceivable use cases should be addressed in Trinity timeframe.