bugfix:Fix fetch PostgresqlTableMetaCache fail when the same table exists in different schemas

[GoodBoyCoder]

• I have registered the PR changes.

Ⅰ. Describe what this PR did

如果SQL表名没有写明schema，使用connection获取当前连接的schema，防止不同schema下存在相同表而导致错误识别多主键

If the SQL table name does not specify schema, use connection to obtain the schema of the current connection to prevent the existence of the same table under different schemas and cause misidentification of multiple primary keys

Ⅱ. Does this pull request fix one issue?

fixes #3098

Ⅲ. Why don't you add test cases (unit test/integration test)?

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

[codecov-commenter]

Codecov Report

Merging #4308 (d1b4b15) into develop (21c103d) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##             develop    #4308      +/-   ##
=============================================
- Coverage      48.53%   48.53%   -0.01%     
- Complexity      3799     3800       +1     
=============================================
  Files            725      725              
  Lines          24305    24306       +1     
  Branches        2984     2984              
=============================================
  Hits           11797    11797              
- Misses         11259    11261       +2     
+ Partials        1249     1248       -1     

Impacted Files	Coverage Δ
...rce/sql/struct/cache/PostgresqlTableMetaCache.java	74.15% <100.00%> (+0.29%)	⬆️
...n/src/main/java/io/seata/common/util/IdWorker.java	77.08% <0.00%> (-6.25%)	⬇️
...in/java/io/seata/server/session/GlobalSession.java	79.31% <0.00%> (+0.43%)	⬆️
...o/seata/server/coordinator/DefaultCoordinator.java	49.35% <0.00%> (+0.43%)	⬆️

[funky-eyes]

LGTM

[jsbxyyx]

LGTM

[slievrly]

LGTM