[Cherry-Pick] unify max_tokens (#4968)

[kxz2002]

• unify max tokens

• modify and add unit test

• modify and add unit test

• modify and add unit tests

---

Motivation

When determining the finish reason, using max_tokens is inaccurate and requires modification.

Modifications

Create new fields max_tokens and max_tokens_list to retrieve the preprocessed max_tokens values.

Usage or Command

No manual command is changed

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!