Enhance debugging of rescheduled notifications

[pierre]

When a notification is re-scheduled, a new notification entry is inserted and the current one archived in the history table, see:

killbill-analytics-plugin/src/main/java/org/killbill/billing/plugin/analytics/AnalyticsListener.java

Line 321 in 98e97ab

if (scheduleAnalyticsJob(job, analyticsConfiguration)) {

Unfortunately, random UUID is used for the user token, so we cannot link the two entries:

killbill-analytics-plugin/src/main/java/org/killbill/billing/plugin/analytics/AnalyticsListener.java

Line 230 in 98e97ab

jobQueue.recordFutureNotification(computeFutureNotificationTime(analyticsConfiguration), job, UUID.randomUUID(), accountRecordId, tenantRecordId);

We should either re-use the same token or use the futureUserToken of the original notification as the user token of the new one.