content_lock_entity_operation doesn't work if the entity list is cached

Patch applies on version 2.3.0 and fixes the issue stated above.

Comment in #8 should still be taken into account but marking this as reviewed since it does work and fixes the issue.
Up to the maintainer to see if they want to implement it this way or not.

I think given #8 we need to come up with a better approach.

Something like the operation adds some other cache tag to the view that we can then use to clear when we need to. This list cache tag is way too generic.

added 'content_lock:' to make it more unique.

@smustgrave the new cache tage should not be specific for an entity ID and we should not clear the entity list cache list here.

Also need to add the cache tag to the break lock operation so that views that use this have the new cache tag in them and are cleared when necessary.

I believe this would be fixed with 🐛 Views entity operations lack cacheability support, resulting in incorrect dropbuttons Needs work in core.