[sglang] fix: rename Sglang to SGLang following SGLang's fashion

[zhaochenyang20]

What does this PR do?

Add concise overview of what this PR aims to achieve or accomplish. Reference related GitHub issues and PRs that help with the review.

As titled.

Checklist Before Starting

• Search for similar PRs. Paste at least one query link here: ...
• Format the PR title as [{modules}] {type}: {description} (This will be checked by the CI)
  • {modules} include fsdp, megatron, sglang, vllm, rollout, trainer, ci, training_utils, recipe, hardware, deployment, ray, worker, single_controller, misc, perf, model, algo, env, tool, ckpt, doc, data
  • If this PR involves multiple modules, separate them with , like [megatron, fsdp, doc]
  • {type} is in feat, fix, refactor, chore, test
  • If this PR breaks any API (CLI arguments, config, function signature, etc.), add [BREAKING] to the beginning of the title.
  • Example: [BREAKING][fsdp, megatron] feat: dynamic batching

Test

For changes that can not be tested by CI (e.g., algorithm implementation, new model support), validate by experiment(s) and show results like training curve plots, evaluation results, etc.

API and Usage Example

Demonstrate how the API changes if any, and provide usage example(s) if possible.

# Add code snippet or script demonstrating how to use this

Design & Code Changes

Demonstrate the high-level design if this PR is complex, and list the specific changes.

Checklist Before Submitting

Important

Please check all the following items before requesting a review, otherwise the reviewer might deprioritize this PR for review.

• Read the Contribute Guide.
• Apply pre-commit checks: pre-commit install && pre-commit run --all-files --show-diff-on-failure --color=always
• Add / Update the documentation.
• Add unit or end-to-end test(s) to the CI workflow to cover all the code. If not feasible, explain why: ...
• Once your PR is ready for CI, send a message in the ci-request channel in the verl Slack workspace.

[gemini-code-assist]

Code Review

This pull request focuses on a simple refactoring: renaming AsyncSglangServer to AsyncSGLangServer. This change is applied consistently across the class definition, its usages in other modules, and the corresponding test suite. The new name AsyncSGLangServer aligns better with other components like SGLangRollout and the SGLang Team name mentioned in copyright headers, thus improving overall code consistency. The changes are correct and self-contained. I have not found any issues of high or critical severity.

[eric-haibin-lin]

If you want to enforce consistency you should add a CI test to check naming style. We should avoid changing class names in the future because it may break other forks code @zhaochenyang20

[zhaochenyang20]

If you want to enforce consistency you should add a CI test to check naming style. We should avoid changing class names in the future because it may break other forks code @zhaochenyang20

Oh. thanks! Is there a name check for verl out of Verl or whatever? 🤔

[eric-haibin-lin]

https://github.com/volcengine/verl/blob/main/.github/workflows/sanity.yml#L85 @zhaochenyang20

[zhaochenyang20]

https://github.com/volcengine/verl/blob/main/.github/workflows/sanity.yml#L85 @zhaochenyang20

thanks so much!