bugfix:fix wrong proxy of datasource bean

[xingfudeshi]

Ⅰ. Describe what this PR did

fix wrong proxy of datasource bean

Ⅱ. Does this pull request fix one issue?

fixes #2322 #2311 #2321

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

I've done integration testing.

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

[codecov-io]

Codecov Report

Merging #2323 into develop will decrease coverage by 0.02%.
The diff coverage is 2.94%.

@@              Coverage Diff              @@
##             develop    #2323      +/-   ##
=============================================
- Coverage      51.74%   51.71%   -0.03%     
+ Complexity      2665     2664       -1     
=============================================
  Files            518      519       +1     
  Lines          16805    16810       +5     
  Branches        2031     2032       +1     
=============================================
- Hits            8695     8694       -1     
- Misses          7293     7298       +5     
- Partials         817      818       +1     

Impacted Files	Coverage Δ	Complexity Δ
...ing/boot/autoconfigure/SeataAutoConfiguration.java	0.00% <0.00%> (ø)	0.00 <0.00> (ø)
...ation/datasource/AutoDataSourceProxyRegistrar.java	0.00% <0.00%> (ø)	0.00 <0.00> (ø)
...ion/datasource/SeataAutoDataSourceProxyAdvice.java	0.00% <0.00%> (ø)	0.00 <0.00> (?)
...on/datasource/SeataAutoDataSourceProxyCreator.java	0.00% <0.00%> (ø)	0.00 <0.00> (?)
...boot/autoconfigure/properties/SeataProperties.java	44.44% <25.00%> (-3.39%)	6.00 <0.00> (ø)
...torage/file/store/FileTransactionStoreManager.java	56.50% <0.00%> (-0.64%)	29.00% <0.00%> (-1.00%)

[ggndnn]

@xingfudeshi
I think this pr is not a final solution of the issues mentioned above, e.g., the cause of #2321 is that seata used cglib to create a proxy instance whose type was a subclass of DynamicDataSource, but it's field resolvedDataSources was not initialized, and more importantly, the proxied bean was not repeatedly proxied before.

So here are some advices:

1. To create proxy in spring way when auto proxying running in spring context, some frameworks assume that the proxy class is created in spring way, e.g., mybatis-plus.
2. To provide include or exclude kind attributes to @EnableAutoDataSourceProxy helping users to control auto proxy target.
   e.g., @EnableAutoDataSourceProxy(include=HikariDataSource.class, exclude= AbstractRoutingDataSource.class), something like this.
3. To recursive check duplication auto proxying, though I am not so sure whether this point is necessary.

[xingfudeshi]

@xingfudeshi
I think this pr is not a final solution of the issues mentioned above, e.g., the cause of #2321 is that seata used cglib to create a proxy instance whose type was a subclass of DynamicDataSource, but it's field resolvedDataSources was not initialized, and more importantly, the proxied bean was not repeatedly proxied before.

So here are some advices:

1. To create proxy in spring way when auto proxying running in spring context, some frameworks assume that the proxy class is created in spring way, e.g., mybatis-plus.
2. To provide include or exclude kind attributes to @EnableAutoDataSourceProxy helping users to control auto proxy target.
   e.g., @EnableAutoDataSourceProxy(include=HikariDataSource.class, exclude= AbstractRoutingDataSource.class), something like this.
3. To recursive check duplication auto proxying, though I am not so sure whether this point is necessary.

Please review.

[ggndnn]

LGTM.

[slievrly]

LGTM