Implement writing entities processing information to the log

Steps:

• subscribe the module to the following events:
  • DI_SRS_MARC_BIB_RECORD_CREATED
  • DI_SRS_MARC_BIB_RECORD_UPDATED
  • DI_SRS_MARC_BIB_RECORD_MODIFIED
  • DI_SRS_MARC_BIB_RECORD_NOT_MATCHED
  • DI_INVENTORY_INSTANCE_CREATED
  • DI_INVENTORY_INSTANCE_UPDATED
  • DI_INVENTORY_INSTANCE_NOT_MATCHED
  • DI_INVENTORY_HOLDING_CREATED
  • DI_INVENTORY_HOLDING_UPDATED
  • DI_INVENTORY_HOLDING_NOT_MATCHED
  • DI_INVENTORY_ITEM_CREATED
  • DI_INVENTORY_ITEM_UPDATED
  • DI_INVENTORY_ITEM_NOT_MATCHED
• expand logic of RecordProcessedEventHandlingServiceImpl to save information about entities creation, update, mismatch to the journal from events specified above, and events about data import completion/error (use eventsChain in DataImportEventPayload)
• add tests

NOTE (from Ann-Marie) If an existing MARC SRS record is updated without any explicit action in the job profile, the log should show "Updated" for the MARC Bib column, instead of "Created." Yes, SRS is creating a new version of the existing MARC SRS, but to the User, the action is assumed to be Update (not Create). The Create action should only appear in the log when a particular record type did not exist before, and after the import, it exists.