Erasing a whole resource does not generate a Notification entry

[d0roppe]

Describe the bug If you have notifications turned on, and you issue an erase of a resource, there is no notification entry issued. There should be a notification entry as this has permanently deleted the resource.

Environment FHIR-main

To Reproduce Monitor notifications, create a resource - Notification is issued then erase the resource - No Notification is issued

Expected behavior Erase of a whole resource should trigger a Notification entry

[lmsurpre]

Potentialy a larger issue with our custom operation framework in general. We now support beforeInvoke and afterInvoke on the FHIRPersistenceInterceptor interface, but the NotificationService doesn't do anything when these are called.

Similar to #2105 but for notification instead of audit. Should be considered together.

[lmsurpre]

Keeping this scoped just to notification of $erase invocations.