Feat: Add support for OpenGauss and Postgres database types

[lgj101]

Description of your changes

Add support for OpenGauss database types

Fixes #

I have:

• Read and followed KubeVela's contribution process.
• Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
• Run yarn lint to ensure the frontend changes are ready for review.
• Run make reviewableto ensure the server changes are ready for review.
• Added backport release-x.y labels to auto-backport this PR if necessary.

[chivalryq]

Thanks for contributing. Please fix the CI.

[chivalryq]

Postgres will be later supported. I think we should leave the import alias as postgresgorm.

[lgj101]

ok let me modify it

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: -11.25% ⚠️

Comparison is base (d0b2a3b) 58.94% compared to head (5fd4c1d) 47.69%.

❗ Current head 5fd4c1d differs from pull request most recent head b35a087. Consider uploading reports for the commit b35a087 to get more accurate results

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #865       +/-   ##
===========================================
- Coverage   58.94%   47.69%   -11.25%     
===========================================
  Files         114      115        +1     
  Lines       19801    20032      +231     
===========================================
- Hits        11671     9554     -2117     
- Misses       6694     9229     +2535     
+ Partials     1436     1249      -187     

Flag	Coverage Δ
apiserver-unittests	?
server-e2e-tests	47.69% <0.00%> (-0.63%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed	Coverage Δ
pkg/server/config/config.go	0.00% <0.00%> (ø)
...rver/infrastructure/datastore/postgres/postgres.go	0.00% <0.00%> (ø)
pkg/server/server.go	53.73% <0.00%> (-0.82%)	⬇️

... and 43 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[NeerajGartia21]

Thanks for your contribution @lgj101 . This PR looks good to me !!
Since the whole implementation of OpenGauss and PostgreSQL are almost similar, I think it is better if we name the driver as PostgreSQL and in the Documentation we can add a note about using OpenGauss as PostgreSQL driver.

CC: @chivalryq

[chivalryq]

Is this really setup a OpenGauss DB? I checked Harmon758/postgresql-action@master...lgj101:opengauss-action:master and it seems to change the exposed variable only. If this is only changes I think we can just uses the origin action and implement the Postgres driver.

After all if we setup a Postgres here we can only checked the compatibility with Postgres. We can't say VelaUX "supports OpenGauss" because we don't have test.

However if we implement the Postgres driver and we can add notes in document that because OpenGauss is compatible with Postgres, you can also use OpenGauss.

[chivalryq]

I'm sorry, yes this action setup a opengauss db. Given the popularity of postgres and the compatibility between them, we can just rename the driver/opengauss to driver/postgresql and keep the openguass test.

[lgj101]

Okay, I have already made the modifications like this

[chivalryq]

LGTM