IBX-85: Fixed Content cache containing invalid "uri" for file field types

[Steveb-p]

Question	Answer
JIRA issue	IBX-85
Bug/Improvement	yes
New feature	no
Target version	7.5
BC breaks	no
Tests pass	yes
Doc needed	no

This fixes the issue of Content sharing field with Site-Access aware/reliant external data.

The root of the issue is that "uri" for BinaryFileField is calculated right after it is acquired from the database, in SPI persistence layer. This causes cache to contain this calculated "uri" value in all SiteAccess' that share the same cache key.

Solution involves:

1. Extending the eZ\Publish\Core\MVC\Symfony\FieldType\BinaryBase\ContentDownloadUrlGenerator with additional methods that would allow recovering of the route and parameters used for the "uri" calculation. A new eZ\Publish\SPI\FieldType\BinaryBase\RouteAwarePathGenerator is introduced to mark their presence.
2. Making eZ\Publish\Core\FieldType\BinaryBase\BinaryBaseStorage::getFieldData, which is called internally by eZ\Publish\Core\Persistence\Legacy\Content\Handler::load, add "route" and "route_parameters" to external data (if RouteAwarePathGenerator is used). They are stored into cache alongside the calculated "uri" for BC compatibility.
3. Have classes descending from eZ\Publish\Core\FieldType\BinaryBase\Type use newly introduced regenerateUri method that recalculates the "uri" from cached "route" and "route_parameters", if they are present.

How to reproduce the issue

1. Add a new Media File
   

2. Either manually clear cache and visit admin file content page, or trigger any admin edit actions that result in cache being regenerated.

3. Observe the URI generated for content.fields in template.
   (vendor/ezsystems/ezplatform-admin-ui/src/bundle/Resources/views/themes/admin/content/location_view.html.twig)
   
   

4. Visit the content location. Observe that the URL in template for content.fields is the same as the one visible in admin. That's the bug. (eZ/Bundle/EzPublishCoreBundle/Resources/views/default/content/full.html.twig)
   
   

Note

Our content field templates do regenerate the URI during rendering (eZ/Bundle/EzPublishCoreBundle/Resources/views/content_fields.html.twig).

TODO:

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

[tomaszszopinski]

QA approved on eZSystems on 2.5.18 with patch.

[lserwatka]

Could you merge it up?