[Docs] vllm/benchmarks/datasets.py fix docstring param format.

[samzong]

Purpose

Ensure BenchmarkDataset docstrings follow the name (type): description format so griffe stops emitting parsing warnings.

WARNING -  griffe: vllm/benchmarks/datasets.py:107: Failed to get 'name: description' pair from 'sampling. Defaults to DEFAULT_SEED.'
--
  | WARNING -  griffe: vllm/benchmarks/datasets.py:237: Failed to get 'name: description' pair from 'request_id_prefix (str) The prefix of the request ids.'
  | WARNING -  griffe: vllm/benchmarks/datasets.py:213: Failed to get 'name: description' pair from 'request_id_prefix (str) The prefix of request_id.'

Test Plan

Test Result

---

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
• (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors.

You ask your reviewers to trigger select CI tests on top of fastcheck CI.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

If you have any questions, please reach out to us on Slack at https://slack.vllm.ai.

🚀

[gemini-code-assist]

Code Review

This pull request addresses docstring formatting issues in vllm/benchmarks/datasets.py to ensure compatibility with documentation generation tools like griffe. The changes are well-executed and correctly fix indentation, parameter descriptions, and cross-referencing syntax within the docstrings. These modifications improve the overall quality and readability of the code documentation. The pull request successfully meets its objective, and I found no high or critical issues in the changes.

[mgoin]

LGTM, thanks!

[windsonsea]

Related to issue #25020

[hmellor]

Thanks for the PR, please use Mkdocs format for the cross references (you've used Sphinx), see https://mkdocstrings.github.io/usage/#cross-references

[mergify]

This pull request has merge conflicts that must be resolved before it can be
merged. Please rebase the PR, @samzong.

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork