Add processing binary binding type

[rabikor]

Updated PR Description

Problem Statement

When using the findBy method in the repository with binary values as parameters, an unhandled error occurs: Unhandled match case 16.

How to reproduce:

$repository->findBy(['uuid' => ['<binary>']]);

This error originates from the following code in the BasicEntityPersister class:
[BasicEntityPersister.php#L1930-L1941](https://github.com/doctrine/orm/blob/3.3.0/src/Persisters/Entity/BasicEntityPersister.php#L1930-L1941).

The current implementation does not handle ParameterType::BINARY properly, leading to unexpected behavior instead of throwing an appropriate exception or processing binary values.

Actual Behavior

• For unsupported parameter types like ParameterType::BINARY, the code fails with Unhandled match case 16.
• This error occurs instead of processing the value or raising an explicit, meaningful exception.
• There is no way to handle this behavior externally due to the unprocessed case in the repository logic.

Expected Behavior

• The system should either:
  1. Process binary values appropriately when passed to the findBy method.
  2. Throw a clear and descriptive exception for unsupported parameter types.
• Ensure compatibility for scalar values (e.g., binary data) within the repository methods.

Changes Made in This PR

• Updated the handling logic in the BasicEntityPersister class to process ParameterType::BINARY correctly.
• Introduced proper exception handling for unsupported parameter types, providing more clarity on the issue to users.
• Ensured backward compatibility for all currently supported parameter types.

Impact of Changes

• Resolves the Unhandled match case 16 error for binary parameters.
• Improves error messaging and developer experience when unsupported parameter types are used.
• Enhances support for handling binary data in findBy methods.

[greg0ire]

You need to update the phpstan baseline, it ignores an issue you addressed.

[derrabus]

Why do we need the default branch here?

[rabikor]

The default is necessary because not all ParameterType cases, such as BOOLEAN, LARGE_OBJECT, or NULL, are supported by ArrayParameterType. The default branch ensures these unsupported types are handled gracefully by throwing a clear exception, preventing unexpected behavior or runtime errors.

[derrabus]

In what situations is this method raising these exception? Is the caller supposed to handle it?

[rabikor]

Doctrine\DBAL\Types\Type::getType method throws Exception

[derrabus]

This answers neither the first nor the second of my questions. 😉

[rabikor]

This method doesn't handle these exceptions directly. I included them to show which ones the method can raise. If you think this is unnecessary, I’ll remove them.

[rabikor]

Exception removed. QueryException throws by this method