Fix boolean types in ProductList::addCondition()

[jremmurd]

Shorthand addCondition() for boolean fields in OpenSearch or ElasticSearch currently result in an error, as the boolean value gets auto converted to string "1".

{"error":{"root_cause":[{"type":"query_shard_exception","reason":"failed to create query: Can't parse boolean value [1], expected [true] or [false]","index":"assortment_de-0","index_uuid":"aVjoKkAaRhCpiHy0515nOA"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"assortment_de-0","node":"R8dCIDExT-2ABMPjIQ-M2w","reason":{"type":"query_shard_exception","reason":"failed to create query: Can't parse boolean value [1], expected [true] or [false]","index":"assortment_de-0","index_uuid":"aVjoKkAaRhCpiHy0515nOA","caused_by":{"type":"illegal_argument_exception","reason":"Can't parse boolean value [1], expected [true] or [false]"}}}]},"status":400}

This PR fixes the typing error (introducing a BC break).

Steps to reproduce

1. add boolean field to index config
2. filter by boolean field using `productList->addCondition($boolValue, $fieldName);
3. Query productlist will result in the error above

Workaround

Pass the strings "true" or "false" in the addCondition() call, as it gets converted to bool values in the query later on.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[herbertroth]

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

[fashxp]

thx very much!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud