IBX-296: Provided new way to handle archived versions

[ViniTou]

Question	Answer
JIRA issue	https://issues.ibexa.co/browse/IBX-296
Bug/Improvement	yes
New feature	yes
Target version	7.5
BC breaks	yes/no
Tests pass	yes
Doc needed	yes

Fix is built from two separate approaches:

1. Disable removing archived versions on publish by using remove_archived_versions_on_publish configuration. That can save some time based on how many versions are going to be removed. If someone knows what he is doing, that process can be moved to scheduled ezplatform:content:cleanup-versions command.

2. There are a lot of expensive count calls with WHERE LIKE to ezimagefile table in \eZ\Publish\Core\FieldType\Image\ImageStorage\Gateway\DoctrineStorage::countImageReferences. As it seems there is no need to use LIKE in current case, new isImageReferenced method was introduced.

but:
3. I have no idea how to implement proper integration tests with changes to content service settings.

QA:

This needs testing in both areas:

• removing archived versions over the limit + new configuration setting
• removing images from filesystem that are no longer related to any content.

TODO:

• Implement feature / fix a bug.
• Implement tests.
• Fix new code according to Coding Standards ($ composer fix-cs).
• Ask for Code Review.

[Steveb-p]

I'm not sure if proper integration tests can be written without introducing a lot of additional code, so 👍 from me.

[Nattfarinn]

I would deprecate current countImageReferences method and provide a proper copy of it without like but eq. We know that our countImageReferences should never be used as it is flawed by design.

[alongosz]

Indeed I don't see easy way to modify that specific config for tests. We need to think about that as a follow up.
One remark:

[kacper-wieczorek-ibexa]

QA Approved - tested on 2.5.21 and 3.3.5

[lserwatka]

You can merge it up now.