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.

Comece revisando os pontos de entrada existentes de update() e as definições de wrapper de pybind11 e nanobind para cada sketch. Determine como as entradas primitivas e os contêineres de itens são distinguidos e, em seguida, decida se a vetorização usa overloads ou um nome de método separado. Está concluído quando todos os sketches derem suporte à iteração do lado do C++ com uma API Python consistente e transparente.

Escrita pelo modelo de indexação a partir do texto da issue.