Feature: Add support for postgres

[frin1]

Add postgres support

• Introduced a dialect field in service structs (DepositService, OrderService, RewardService, TradeService, WithdrawService) to handle database-specific SQL generation.
• Added ensureDialect method to initialize the dialect if not set.
• Updated SQL queries to use dialect-aware methods for table and column names, ensuring compatibility with MySQL and PostgreSQL.
• Refactored insert and upsert logic to utilize dialect-specific UUID handling and SQL generation.
• Improved test coverage for PostgreSQL dialect handling in RewardService and TradingVolume queries.
• Added a new configuration file for PostgreSQL connection settings.

[CLAassistant]

All committers have signed the CLA.

[c9s]

You need to use the migration tool c9s/rockhopper and make sure this PR works well with rockhopper

[c9s]

Also, could you please split the changes like fixes should be in another PR

For supporting postgresql, it could be incremental backward compatible changes in multiple PRs, it doesn't have to be in one large PR

[frin1]

You need to use the migration tool c9s/rockhopper and make sure this PR works well with rockhopper

For creating go code from the migrations, I used rockhopper compile --config rockhopper_postgres.yaml --output pkg/migrations/postgres. Is there anything else I need to do with rockhopper?

[frin1]

Also, could you please split the changes like fixes should be in another PR

For supporting postgresql, it could be incremental backward compatible changes in multiple PRs, it doesn't have to be in one large PR

I have reverted the fixes.

[c9s]

Thanks for your pull request,

but CI build failed, could you please check? thanks

Upgrading Go is acceptable, but you need to split the PRs and each one should focus on its topic

for example, this commit 7bdeebb is not related to postgres.

since this project is used by many companies on production, we would prefer low impact PR comes first.