[Cherry-Pick] Fix process_response_dict to support async in serving_completion (#5758)

[kxz2002]

…tion (#5758)

• support process_response_dict async initial commit

• fixbug

• add unit test

• optimize

Motivation

The process_response_dict function in serving_completion.py does not support asynchronous calls, which causes issues when using EB5's processor.

💡 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)

Modifications

Add a check to determine whether the process_response_dict function is an asynchronous call, enabling support for asynchronous invocations.

Usage or Command

no change in user command.

Accuracy Tests

no need

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

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (release/2.4@c170fc4). Learn more about missing BASE report.

Additional details and impacted files

@@              Coverage Diff               @@
##             release/2.4    #5802   +/-   ##
==============================================
  Coverage               ?   59.09%           
==============================================
  Files                  ?      328           
  Lines                  ?    40738           
  Branches               ?     6206           
==============================================
  Hits                   ?    24073           
  Misses                 ?    14787           
  Partials               ?     1878           

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

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.