Fix the support for custom parameter types in native queries

[stof]

The Query class (used for DQL queries) takes care of using the value and type as is when a type was specified for a parameter instead of going through the default processing of values.
The NativeQuery class was missing the equivalent check, making the custom type work only if the default processing of values does not convert the value to a different one.

[greg0ire]

Can you please add a test for this? 🙏

[stof]

@greg0ire I added a test similar to the test added in #7528 (which fixed it for DQL queries), which uses a mock to ensure that one part of the value processing is never called in the test.
This is not 100% reliable (if we refactor the value processing to perform checks in a different way, we might end up regressing this fix without failing the test) but it is a lot easier than using a cross-platform functional test which would lead to a failure during the query execution when the custom type does not convert the value (my own use case which broke because of a bug relies on a custom DBAL type which is compatible only with the postgresql platform)

[derrabus]

Why?

[greg0ire]

@derrabus no reason I think. Removed.

[stof]

I created this file by copying another one, and I forgot to remove that trait

[greg0ire]

Thanks @stof !