fix(postgres): Handle case-sensitive column names

[david-pivonka]

This PR fixes an issue where camelCased column names in PostgreSQL were not being handled correctly, leading to query errors.

[julien040]

Hello @david-pivonka,
Thank you for opening this pull request!

Can you detail what kind of issues you were encountering? I tried to reproduce the issue on my computer, but I couldn't. The query worked with and without the patch.

-- Run on PostgreSQL
CREATE TABLE a (
	id VARCHAR PRIMARY KEY,
	myAge INTEGER,
	myName VARCHAR
);

-- Run on Anyquery
SELECT * FROM a

Or is it with a table that has two columns, with one camel-cased? Because SQLite (which Anyquery is based on) converts both to mycol, and it fails.

CREATE TABLE test (
    mycol INT,
    "MyCol" INT
);

Anyway, I'm still going to merge this pull request because Anyquery should always pass the escaped identifier to the end database. I'm just curious.