optimize: file mode does not require lazy processing of sessions

[funky-eyes]

• I have registered the PR changes.

Ⅰ. Describe what this PR did

目前的实现中,在同步二阶段时不会进行删除全局事务为了避免db和redis下残留branchsession和lock所以进行了默认2分10秒延迟删除,但是file下globalsession是有锁的,不会出现这种残留情况,也就无需延迟,仅需异步删除即可,file的内存是寸土寸金应尽快删除,所以需要通过storemode判断处理

Ⅱ. Does this pull request fix one issue?

fixes #4399

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

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

[slievrly]

LGTM

[codecov-commenter]

Codecov Report

Merging #4407 (c41cac1) into develop (4622746) will decrease coverage by 0.00%.
The diff coverage is 16.66%.

@@              Coverage Diff              @@
##             develop    #4407      +/-   ##
=============================================
- Coverage      48.76%   48.76%   -0.01%     
+ Complexity      3967     3965       -2     
=============================================
  Files            733      733              
  Lines          25182    25185       +3     
  Branches        3132     3135       +3     
=============================================
  Hits           12281    12281              
- Misses         11598    11602       +4     
+ Partials        1303     1302       -1     

Impacted Files	Coverage Δ
...o/seata/server/coordinator/DefaultCoordinator.java	50.54% <16.66%> (-1.30%)	⬇️
...in/java/io/seata/server/session/GlobalSession.java	78.65% <0.00%> (ø)
...in/java/io/seata/server/session/SessionHelper.java	74.71% <0.00%> (+2.29%)	⬆️