Vectorize update()

Looping in python is slow. We should enable `update()` with multiple inputs where C++ handles the iteration, for all sketches.

For sketches that take primitive types this is simple and can be done by overloading `update()`. For item containers it may be less straightforward since a list is a type of object, meaning an overloaded may treat the list as a single thing to ingest.

IIRC, the wrappers (both pybind11 and nanobind) iterate through the possible methods in the order ini which they were declared in the wrapper definition, which is not good for API design: Lack of transparency, internal rearranging of code can cause side-effects, etc. So we probably need a different method name. Then we run into the question of whether we should use an overload where practical and a different name where necessary or if we go for more consistency.

首先檢視現有的 update() 進入點，以及每個 sketch 的 pybind11 與 nanobind wrapper 定義。判斷如何區分原始輸入與 item 容器，接著確定向量化是使用多載還是獨立的方法名稱。完成的標準是所有 sketch 都支援 C++ 端迭代，並提供一致且透明的 Python API。

由索引模型根據 Issue 內容生成。