Add logging for delete action

Hi, thanks for your work on the subject @Dave Reid.

2 things:

1. Execute method should return results that can be grouped, otherwise you may get a lot of messages when action is executed, the returned value should be as it was or maybe grouped into entity types.
2. Use dependency injection for logger service (example constructor and create methods can be found in views_bulk_edit module action), the logger() method will not be needed.

I rerolled the patch for 8.x-3.x-dev and made the requested changes.

Nice, but this should be configurable in the View admin (see ViewsBulkOperationsPreconfigurationInterface), imagine someone deleting 100 000 entities in a bulk operation and getting this many log entries..

Adding Reroll patch for 4.3.x
I dont seem to be able to push to push to issue fork. Im sure im doing it wrong :P

Left a review, also please make sure all checks are green.

Ok, I left the review on https://git.drupalcode.org/project/views_bulk_operations/-/merge_request... but it also applies to the latest branch.

I've taken the patch from #10 and put it into https://git.drupalcode.org/project/views_bulk_operations/-/merge_request...

Great but please see my notes on the other MR that also apply.

Thank you, Looks good!

I have one more concern: what if someone deletes a lot of entities - do we still want to log all that? I think we may leave it as is for the time being though and if someone's log will be flooded and they don't like that they can always create a follow-up to make it configurable.

I'll let it lay for a week or so in case someone else had any feedback.

Thanks - that sounds like a good way forward.

If we do make it configurable, I'd suggest that the default is that logging is enabled.

I was surprised when I realised that nodes deleted this way weren't logged - I'd say it's better to be consistent with core, which does log individual node deletion.