[refactor] improve ConstantList exception specificity

[skyloevil]

Replace generic Exception with TypeError for all mutating operations in ConstantList class. This provides more precise error semantics as these operations attempt to modify an immutable data structure, which is fundamentally a type compatibility issue.

Changes:

• append, extend, insert, pop, remove, clear methods
• setitem and delitem magic methods

This improves error handling precision and follows Python best practices for exception types.

[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 can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

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.

🚀

[gemini-code-assist]

Code Review

This pull request correctly refactors the ConstantList class to raise TypeError instead of a generic Exception for mutating operations. This is a good improvement as it provides more specific and standard error semantics for an immutable collection. I've added a couple of high-severity comments to address incorrect method signatures for insert and pop, which, if corrected, will ensure the class behaves consistently with Python's built-in list and raises the intended errors.

[gemini-code-assist]

The insert method signature is incorrect. It should match the list.insert(index, object) signature to correctly override the behavior and provide the intended TypeError. The current signature insert(self, item) takes only one argument besides self, which will cause a TypeError about the number of arguments if a user tries to call it like list.insert(0, value), preventing the intended "Cannot insert..." error from being raised.

Suggested change

	def insert(self, item):
	def insert(self, index, item):

[gemini-code-assist]

The pop method signature is incorrect. It should match list.pop([index]), which takes an optional index argument. The current signature pop(self, item) requires one argument, which is inconsistent with list.pop() that can be called with zero or one argument (the index). This will lead to unexpected TypeError exceptions related to arguments, rather than the intended one about immutability.

Suggested change

	def pop(self, item):
	def pop(self, index=-1):