Remove base64 asset data when indexing wysiwyg fields

[BlackbitDevs]

If you have a wysiwyg field in a data object, it can have HTML content like

<p>Some text</p>
<p><img src="blob:https://www.igp-powder.com/80000760-05b3-4ee8-aad8-2a263cd65829" alt=""></p>
<p>Some other text</p>

In the corresponding database table the image gets saved base64-encoded:

<p>Some text</p>
<p><img src="data:image/jpeg;base64,/9j/4AAQSkZJRgABAQ..."
<p>Some other text</p>

In our case this was a huge original image, so the base64 was > 50 MB.

When the object with this data is tried to be indexed, open search throws an error

symfony-messenger    14:11:47 WARNING   [pimcore.opensearch] Request Failure: ["method" => "POST","uri" => "https://opensearch-1.opensearch:9200/_bulk?refresh=wait_for","port" => 9200,"headers" => ["Host" => ["opensearch-1.opensearch"],"Content-Type" => ["application/json"],"Accept" => ["application/json"],"User-Agent" => ["opensearch-php/2.3.1 (Linux 6.1.124; PHP 8.2.27)"]],"HTTP code" => 413,"duration" => 0.001124,"error" => "Unknown 413 error from OpenSearch """]

HTTP 413 means "Content too large".

As the generic data index is used for searching, imho it does not make sense to store base64 information there. So this PR removes the base64 data from the Wysiwyg HTML.

[BlackbitDevs]

Are the failing tests caused by this PR?

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[herbertroth]

@BlackbitDevs Could you please rebase this PR to the 2.x branch? There won’t be a 1.x release. Thanks!

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[BlackbitDevs]

I think it worked because you changed the base branch of this PR. If there is anything for me to do, please notify me again.