fix: parse text[] as array<string>

[adrienbrault]

Hey,

The way MartinGeorgiev\Doctrine\DBAL\Types\TextArray converts database values to php floats/int broke my expectations.

When I save ['a', '1', '0.1'] to my database, I expect to get back the same ['a', '1', '0.1'], NOT ['a', 1, 0.1]. Especially when the column name is "text".

I also checked postgres itself, and there is no magic casting:

database=# select pg_typeof(('{0.4}'::text[])[1]);
 pg_typeof
-----------
 text
(1 row)

[greptile-apps]

PR Summary

This PR fixes type handling in PostgreSQL text arrays by ensuring numeric values remain as strings rather than being automatically converted to integers/floats.

• Modified src/MartinGeorgiev/Utils/DataStructure.php to preserve string types for numeric values in text arrays
• Updated tests/MartinGeorgiev/Doctrine/DBAL/Types/TextArrayTest.php to use strict type checking with assertSame()
• Adjusted test data in tests/MartinGeorgiev/Utils/DataStructureTest.php to properly handle numeric values as strings
• Aligned behavior with PostgreSQL's native text[] type which maintains all elements as strings

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

_{3 file(s) reviewed, 2 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

logic: Error message mentions expecting integer/float values but code no longer handles these types

[greptile-apps]

logic: Mismatch between test data - phpValue has '604' as string but postgresValue has 604 as unquoted number. This will cause type inconsistency.

[martin-georgiev]

Why was this changed?

[martin-georgiev]

Why was this changed?