[Cherry-Pick] add a new reasoning parser (#4571)

[kxz2002]

• add new reasoning_parser initial commit

• add parser file content

• add register

• ernie_test_reasoning_parser

• support <tool_call> token and add tool_parser

• add and fix unit tests

• modify reasoning_parser

• modify reasoning parser and tool parser

• modify unit tests

• modify reasoning_parser and tool_parser

• modify unit tests

• fix tool_parser

• modify the logic of reasoning_parser and tool_parser

• add and modify unit tests

• standardize code style

• simplify reasoning_parser and tool_parser

• modify unit test

Motivation

Add a new reasoning_parser
The model's output format with reasoning includes two types:
No tool invocation: xxxyyy
Tool invocation: xxx\n<tool_call>zzz</tool_cal>
x represents the reasoning content, y represents the response content, and z represents the tool invocation content.

Modifications

Add a new reasoning_parser ErnieTestReasoningParser

Usage or Command

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!

[LiqinruiG]

LGTM