optimize: optimize get select for update recognizer

[l81893521]

Ⅰ. Describe what this PR did

When I use PG Sql in the feature branch, I found could not use one way to determine the SQL is for update or not. So, we have to use different way for different database.

Ⅱ. Does this pull request fix one issue?

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

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

[codecov-io]

Codecov Report

Merging #1979 into develop will decrease coverage by 0.02%.
The diff coverage is 100%.

@@              Coverage Diff              @@
##             develop    #1979      +/-   ##
=============================================
- Coverage      55.29%   55.26%   -0.03%     
+ Complexity      2432     2430       -2     
=============================================
  Files            432      432              
  Lines          14436    14439       +3     
  Branches        1707     1706       -1     
=============================================
- Hits            7982     7980       -2     
- Misses          5733     5735       +2     
- Partials         721      724       +3

Impacted Files	Coverage Δ	Complexity Δ
...source/sql/druid/MySqlOperateRecognizerHolder.java	100% <100%> (ø)	7 <2> (+1)	⬆️
...ql/druid/oracle/OracleOperateRecognizerHolder.java	100% <100%> (ø)	7 <2> (+1)	⬆️
.../io/seata/rm/datasource/sql/SQLVisitorFactory.java	82.35% <100%> (-0.99%)	5 <0> (-1)
...server/store/file/FileTransactionStoreManager.java	56.5% <0%> (-0.96%)	29% <0%> (ø)
...in/java/io/seata/server/session/GlobalSession.java	84.54% <0%> (-0.49%)	67% <0%> (-1%)
...o/seata/server/coordinator/DefaultCoordinator.java	48.01% <0%> (-0.4%)	27% <0%> (-2%)

[slievrly]

LGTM

[zjinlei]

LGTM