[Misc] Use VLLMValidationError in batch, pooling, and tokenize protocol validators

[umut-polat]

Replaces ValueError with VLLMValidationError in the remaining protocol model validators across three files:

• run_batch.py: validate_no_file in BatchTranscriptionRequest and BatchTranslationRequest → parameter: file
• pooling/base/protocol.py: check_generation_prompt → parameter: continue_final_message
• tokenize/protocol.py: check_generation_prompt → parameter: continue_final_message

This completes the VLLMValidationError migration across all protocol-level model validators in the OpenAI-compatible endpoints.

Previous PRs in this series: #35456, #35510, #35664, #35666, #36254.

[mergify]

Hi @umut-polat, the pre-commit checks have failed. Please run:

uv pip install pre-commit
pre-commit install
pre-commit run --all-files

Then, commit the changes and push to your branch.

For future commits, pre-commit will run automatically on changed files before each commit.

Tip

Is mypy or markdownlint failing?

mypy and markdownlint are run differently in CI. If the failure is related to either of these checks, please use the following commands to run them locally:

# For mypy (substitute "3.10" with the failing version if needed)
pre-commit run --hook-stage manual mypy-3.10
# For markdownlint
pre-commit run --hook-stage manual markdownlint

[gemini-code-assist]

Code Review

This pull request continues the effort to standardize error handling by replacing ValueError with the custom VLLMValidationError in several protocol validators. The changes are generally good, but I've identified a potential improvement in how validation errors for conflicting parameters are reported. In pooling/base/protocol.py and serve/tokenize/protocol.py, the error points to a single parameter when two are in conflict, which could be misleading. I've suggested removing the specific parameter from the error to make it more accurate, albeit less specific.

[gemini-code-assist]

The validation error is raised when both continue_final_message and add_generation_prompt are True. However, the parameter argument for VLLMValidationError is set only to "continue_final_message". This can be misleading for API clients that use this field to highlight the source of the error, as the issue stems from the combination of two parameters. To avoid ambiguity, consider omitting the parameter argument for this validation check. This makes the structured error less specific but more accurate.

            raise VLLMValidationError(
                "Cannot set both `continue_final_message` and "
                "`add_generation_prompt` to True."
            )

[mergify]

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

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

[mergify]

Hi @umut-polat, the pre-commit checks have failed. Please run:

uv pip install pre-commit
pre-commit install
pre-commit run --all-files

Then, commit the changes and push to your branch.

For future commits, pre-commit will run automatically on changed files before each commit.

Tip

Is mypy failing?

mypy is run differently in CI. If the failure is related to this check, please use the following command to run it locally:

# For mypy (substitute "3.10" with the failing version if needed)
pre-commit run --hook-stage manual mypy-3.10

[DarkLight1337]

Sorry for the delay!