[New][RL] Support Rollout Routing Replay

[gongshaotian]

Motivation

💡 If this PR is a Cherry Pick, the PR title needs to follow the format by adding the [Cherry-Pick] label at the very beginning and appending the original PR ID at the end. For example, [Cherry-Pick][CI] Add check trigger and logic(#5191)

💡 如若此PR是Cherry Pick，PR标题需遵循格式，在最开始加上[Cherry-Pick]标签，以及最后面加上原PR ID，例如[Cherry-Pick][CI] Add check trigger and logic(#5191)

In RL training tasks, we have enabled recording of routing information during the inference process and directly utilized the experts selected during inference in the training process to alleviate the consistency issue between training and inference.

0908 branch: #5166

Modifications

Add RoutingReplayManager and RoutingStore class to support routing replay

• RoutingStore: The client used for interacting with Routing Store has two routing storage modes based on File System and RDMA(WIP).
• RoutingReplayManager: Implement request level routing table management within FastDeploy.

Feature support:

• CUDAGraph
• PrefixCache
• ChunkedPrefill
• Speculative Decoding
• PD Disaggregation

Model support:

• EB5
• EB4.5
• GLM

Usage or Command

Add a startup switch for route replay：

    --routing-replay-config '{"enable_routing_replay":true, "routing_store_type":"local", "local_store_dir":"xxx/routing_replay_output"}'

And only support chatcmpl API.

Accuracy Tests

Checklist

• Add at least a tag in the PR title.
  • Tag list: [[FDConfig],[APIServer],[Engine], [Scheduler], [PD Disaggregation], [Executor], [Graph Optimization], [Speculative Decoding], [RL], [Models], [Quantization], [Loader], [OP], [KVCache], [DataProcessor], [BugFix], [Docs], [CI], [Optimization], [Feature], [Benchmark], [Others], [XPU], [HPU], [GCU], [DCU], [Iluvatar], [Metax]]
  • You can add new tags based on the PR content, but the semantics must be clear.
• Format your code, run pre-commit before commit.
• Add unit tests. Please write the reason in this PR if no unit tests.
• Provide accuracy results.
• If the current PR is submitting to the release branch, make sure the PR has been submitted to the develop branch, then cherry-pick it to the release branch with the [Cherry-Pick] PR tag.

[paddle-bot]

Thanks for your contribution!

[codecov-commenter]

Codecov Report

❌ Patch coverage is 59.03614% with 102 lines in your changes missing coverage. Please review.
⚠️ Please upload report for BASE (develop@c45e064). Learn more about missing BASE report.

Files with missing lines	Patch %	Lines
...model_executor/layers/moe/routing_indices_cache.py	56.75%	59 Missing and 5 partials ⚠️
...el_executor/layers/moe/fused_moe_triton_backend.py	11.11%	6 Missing and 2 partials ⚠️
..._executor/layers/moe/fused_moe_deepgemm_backend.py	0.00%	7 Missing ⚠️
...del_executor/layers/moe/fused_moe_wint2_backend.py	0.00%	5 Missing ⚠️
fastdeploy/model_executor/layers/moe/moe.py	76.19%	4 Missing and 1 partial ⚠️
...l_executor/layers/moe/fused_moe_cutlass_backend.py	42.85%	4 Missing ⚠️
fastdeploy/engine/args_utils.py	70.00%	2 Missing and 1 partial ⚠️
...el_executor/layers/moe/fused_moe_marlin_backend.py	0.00%	3 Missing ⚠️
...odel_executor/layers/moe/fused_moe_backend_base.py	50.00%	2 Missing ⚠️
fastdeploy/worker/gpu_model_runner.py	94.11%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             develop    #5405   +/-   ##
==========================================
  Coverage           ?   59.09%           
==========================================
  Files              ?      327           
  Lines              ?    40560           
  Branches           ?     6154           
==========================================
  Hits               ?    23967           
  Misses             ?    14745           
  Partials           ?     1848           

Flag	Coverage Δ
GPU	59.09% <59.03%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.