bugfix: After 1.6.0, auto-increment of pgsql/oracle pk columns are no longer supported

[isharpever]

• I have registered the PR changes.

Ⅰ. Describe what this PR did

fix：1.6.0~1.6.1，AT模式，当insert语句不包含主键列时，无法获取到pgsql/oracle的自增主键值。

Ⅱ. Does this pull request fix one issue?

fixes #5264

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

添加下面几个单测
io.seata.rm.datasource.exec.PostgresqlInsertExecutorTest#testGetPkValues_SinglePk
io.seata.rm.datasource.exec.PostgresqlInsertExecutorTest#testGetPkValues_MultiPk
io.seata.rm.datasource.exec.PostgresqlInsertExecutorTest#testContainsAnyPK
io.seata.rm.datasource.exec.OracleInsertExecutorTest#testGetPkValues_SinglePk
io.seata.rm.datasource.exec.OracleInsertExecutorTest#testGetPkValues_MultiPk

Ⅳ. Describe how to verify it

集成测试验证了下面几种情况

    /*
     * 单主键场景
     * 表: single
     * 列: id, name
     * 主键: id
     */
    // insert columns为空：从插入行获取主键值
    jdbcTemplate.update("insert into single values(1, ?)", name);

    // insert columns包含主键：从插入行获取主键值
    jdbcTemplate.update("insert into single(id, name) values(2, ?)", name);

    // insert columns不是空, 且不包含主键：获取自增值
    jdbcTemplate.update("insert into single(name) values(?)", name);

    /*
     * 多主键场景
     * 表: multi
     * 列: id1, id2, name
     * 联合主键: (id1, id2)
     */
    // insert columns为空：从插入行获取全部主键值
    jdbcTemplate.update("insert into multi values(1, 1, ?)", name);

    // insert columns包含全部主键：从插入行获取全部主键值
    jdbcTemplate.update("insert into multi(id1, id2, name) values(2, 2, ?)", name);

    // insert columns包含部分主键：从插入行获取存在的主键值，其他获取自增值
    jdbcTemplate.update("insert into multi(id1, name) values(3, ?)", name);
    jdbcTemplate.update("insert into multi(id2, name) values(4, ?)", name);

    // insert columns不是空, 且不包含主键：全部主键都获取自增值
    jdbcTemplate.update("insert into multi(name) values(?)", name);

Ⅴ. Special notes for reviews

[CLAassistant]

All committers have signed the CLA.

[codecov-commenter]

Codecov Report

Merging #5284 (6397724) into develop (cee99cd) will increase coverage by 0.06%.
The diff coverage is 96.29%.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@              Coverage Diff              @@
##             develop    #5284      +/-   ##
=============================================
+ Coverage      48.73%   48.79%   +0.06%     
- Complexity      4159     4174      +15     
=============================================
  Files            743      743              
  Lines          26590    26615      +25     
  Branches        3321     3330       +9     
=============================================
+ Hits           12958    12987      +29     
+ Misses         12232    12226       -6     
- Partials        1400     1402       +2     

Impacted Files	Coverage Δ
...o/seata/rm/datasource/exec/BaseInsertExecutor.java	63.43% <88.88%> (+1.50%)	⬆️
...m/datasource/exec/oracle/OracleInsertExecutor.java	81.48% <100.00%> (+7.79%)	⬆️
...urce/exec/postgresql/PostgresqlInsertExecutor.java	62.79% <100.00%> (+11.36%)	⬆️
...er/src/main/java/io/seata/server/ServerRunner.java	50.00% <0.00%> (-15.39%)	⬇️
...torage/file/store/FileTransactionStoreManager.java	59.16% <0.00%> (-0.65%)	⬇️
...erver/storage/file/session/FileSessionManager.java	48.40% <0.00%> (+0.63%)	⬆️
...in/java/io/seata/server/session/GlobalSession.java	79.77% <0.00%> (+0.76%)	⬆️
.../java/io/seata/server/coordinator/DefaultCore.java	50.58% <0.00%> (+2.35%)	⬆️
...o/seata/server/session/AbstractSessionManager.java	64.17% <0.00%> (+2.98%)	⬆️

[funky-eyes]

Can you separate the oracle and pgsql modified code into 2 pr commits? This will make it easier for us to review

[isharpever]

Can you separate the oracle and pgsql modified code into 2 pr commits? This will make it easier for us to review

ok

[funky-eyes]

close by #5288 #5287