refactor: add sql parser type druid as constant

[ggndnn]

Ⅰ. Describe what this PR did

According to the last review comment in #1703, added sql parser type druid as constant.

Ⅱ. 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 #2156 into develop will increase coverage by 0.03%.
The diff coverage is 100%.

@@              Coverage Diff              @@
##             develop    #2156      +/-   ##
=============================================
+ Coverage      54.39%   54.42%   +0.03%     
- Complexity      2469     2470       +1     
=============================================
  Files            445      445              
  Lines          14742    14742              
  Branches        1734     1734              
=============================================
+ Hits            8019     8024       +5     
+ Misses          5963     5957       -6     
- Partials         760      761       +1

Impacted Files	Coverage Δ	Complexity Δ
...ava/io/seata/core/constants/ConfigurationKeys.java	0% <ø> (ø)	0 <0> (ø)	⬇️
...va/io/seata/sqlparser/druid/DruidDbTypeParser.java	100% <ø> (ø)	2 <0> (ø)	⬇️
...eata/server/store/db/DruidDataSourceGenerator.java	0% <ø> (ø)	0 <0> (ø)	⬇️
...ata/sqlparser/druid/DruidSQLRecognizerFactory.java	47.05% <ø> (ø)	2 <0> (ø)	⬇️
...in/java/io/seata/rm/datasource/util/JdbcUtils.java	87.5% <100%> (ø)	3 <0> (ø)	⬇️
.../io/seata/rm/datasource/sql/SQLVisitorFactory.java	80% <100%> (ø)	2 <1> (ø)	⬇️
...in/java/io/seata/server/session/GlobalSession.java	84.13% <0%> (-0.49%)	67% <0%> (-1%)
...o/seata/server/coordinator/DefaultCoordinator.java	47.26% <0%> (-0.4%)	28% <0%> (ø)
...server/store/file/FileTransactionStoreManager.java	56.5% <0%> (+0.31%)	29% <0%> (ø)	⬇️
...mon/src/main/java/io/seata/common/util/IOUtil.java	70% <0%> (+10%)	3% <0%> (ø)	⬇️
... and 1 more

[zjinlei]

Could it be an enumeration class that put more sql parser types?

[ggndnn]

Could it be an enumeration class that put more sql parser types?

How about an abstract class contains sql parser type constants? Because @LoadLevel(name = "druid") needs constants. Any suggestion?

[slievrly]

LGTM. We may need to move ConfigurationKeys to the common module.

[zjinlei]

Could it be an enumeration class that put more sql parser types?

How about an abstract class contains sql parser type constants? Because @LoadLevel(name = "druid") needs constants. Any suggestion?

Enumeration attributes are constants, so why not consider it?
I think it is possible to build a SqlParserType class in seata-sqlparser-core.

[ggndnn]

Could it be an enumeration class that put more sql parser types?

How about an abstract class contains sql parser type constants? Because @LoadLevel(name = "druid") needs constants. Any suggestion?

Enumeration attributes are constants, so why not consider it?
I think it is possible to build a SqlParserType class in seata-sqlparser-core.

@LoadLevel(name= needs String type constants. I'm not sure how to add enum to it, so my suggestion is to create an abstract class SqlParserType contains string type constants or just use ConfigurationKeys.

public @interface LoadLevel {
    /**
     * Name string.
     *
     * @return the string
     */
    String name();

    /**
     * Order int.
     *
     * @return the int
     */
    int order() default 0;
}

[ggndnn]

LGTM. We may need to move ConfigurationKeys to the common module.

This can be considered.

[ggndnn]

LGTM. We may need to move ConfigurationKeys to the common module.

This can be considered.

@slievrly
Need to do this in this pr or in future pr after more extensive discussion?

[zjinlei]

ConfigurationKeys

Sorry, My low-level mistake.
But it is only a constant, not a configuration key, and there will be more sql parser types, I don't think it should be put in ConfigurationKeys.
Hope that there is a better way, can list more sql parser later.

[ggndnn]

ConfigurationKeys

Sorry, My low-level mistake.
But it is only a constant, not a configuration key, and there will be more sql parser types, I don't think it should be put in ConfigurationKeys.
Hope that there is a better way, can list more sql parser later.

@zjinlei

SqlParserType added.

[zjinlei]

LGTM