Fixed Ratis server RPC timeout parameter setting invalidation bug

[OneSizeFitsQuorum]

Phenomenon：

• Our Ratis RPC timeout parameter is only applied to the Client, not to the Server.
• This results in the following RPC timeout still being 3s, which we actually set to 10s in the parameter
  

Solution：

• Set the corresponding parameters when starting the Ratis Server

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication

[codecov-commenter]

Codecov Report

Merging #11418 (2a75101) into master (b13edf3) will decrease coverage by 0.01%.
Report is 1 commits behind head on master.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master   #11418      +/-   ##
============================================
- Coverage     48.57%   48.56%   -0.01%     
+ Complexity    24451    24449       -2     
============================================
  Files          2817     2817              
  Lines        173143   173144       +1     
  Branches      20672    20672              
============================================
- Hits          84100    84094       -6     
- Misses        89043    89050       +7     

Files	Coverage Δ
.../org/apache/iotdb/consensus/ratis/utils/Utils.java	99.34% <100.00%> (+<0.01%)	⬆️

... and 16 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more