IBX-8309: the order of str_replace execution has been changed to match what was before the changes

[mateuszdebinski]

🎫 Issue	IBX-8309

Before the changes we had str_replace which looked like this:

 $resolver = str_replace(
            [
                'content',
                'location',
                'item',
                'field',
            ],
            [
                'value.getContent()',
                'value.getLocation()',
                'value',
                'resolver("DomainFieldValue", [value, "' . $fieldDefinition->identifier . '"])',
            ],
            $resolver
        );

which did not replace the identifiers of fields that contained strings such as: content, location, item.
After changes, we first change the field to the resolver(... and then we use str_replace to replace the rest, which causes even the field identifiers to be changed. to prevent this, I moved str_replace before replace field to resolver(... so that it does not affect the identifiers

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[konradoboza]

Looks ok, but please double check all the scenarios coming from: https://issues.ibexa.co/browse/IBX-7979 when testing.

[wizhippo]

Looks to be the same as https://issues.ibexa.co/browse/IBX-8116 also