Callback mode supports default rejection policy adjustment

[JervyShi]

Motivation:

Fix #1131

Modification:

Describe the idea and modifications you've done.

Result:

Fixes #.

If there is no issue then describe the changes introduced by this PR.

[JervyShi]

Link sofastack/sofa-bolt#265

[codecov]

Codecov Report

Merging #1132 (ac6ffeb) into master (de7a124) will increase coverage by 0.06%.
The diff coverage is 96.87%.

@@             Coverage Diff              @@
##             master    #1132      +/-   ##
============================================
+ Coverage     70.79%   70.85%   +0.06%     
+ Complexity      830      828       -2     
============================================
  Files           405      405              
  Lines         17088    17100      +12     
  Branches       2669     2669              
============================================
+ Hits          12098    12117      +19     
+ Misses         3607     3597      -10     
- Partials       1383     1386       +3     

Impacted Files	Coverage Δ
...in/java/com/alipay/sofa/rpc/common/RpcOptions.java	100.00% <ø> (ø)
.../sofa/rpc/message/bolt/AbstractInvokeCallback.java	91.17% <87.50%> (-1.14%)	⬇️
...ava/com/alipay/sofa/rpc/config/ConsumerConfig.java	77.64% <100.00%> (+0.53%)	⬆️
...java/com/alipay/sofa/rpc/module/LookoutModule.java	52.38% <0.00%> (-33.34%)	⬇️
...a/com/alipay/sofa/rpc/common/utils/ClassUtils.java	78.23% <0.00%> (-2.05%)	⬇️
...lipay/sofa/rpc/registry/consul/ConsulRegistry.java	47.25% <0.00%> (-0.55%)	⬇️
...va/com/alipay/sofa/rpc/client/AbstractCluster.java	69.63% <0.00%> (-0.53%)	⬇️
...n/java/com/alipay/sofa/rpc/common/SofaConfigs.java	86.79% <0.00%> (+1.88%)	⬆️
...y/sofa/rpc/transport/bolt/BoltClientTransport.java	85.71% <0.00%> (+2.48%)	⬆️
.../main/java/com/alipay/sofa/rpc/event/EventBus.java	80.39% <0.00%> (+7.84%)	⬆️
... and 2 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update de7a124...ac6ffeb. Read the comment docs.

[EvenLjj]

LGTM

[OrezzerO]

Wait time will be 100 * invokeCount ms, if invokeCount==100 ,this case will run 10s. It is too long

[JervyShi]

This is the worst case time consumption, the actual execution time should be (invokeCount / max_threadNum)*100 or so, latch await will stop when count is 0, I have tried to use this time consumption, in the local execution of about 1s, but because of the CI machine performance is poor, the execution is easy to execute before the completion of the timeout results in test case failure, so I modified the maximum wait time.

[OrezzerO]

LGTM