More Pythonic VTK wrapping

Hrm. While it is the most common case, does this mean we’ll have an ambiguity if we return some algorithm result as a tuple itself in the future (say we start using std::tuple in VTK)? Do the bindings know this that they can write it into the .pyi or __doc__ for the attribute/method? I know dealing with (vtkobject,) in the vastly common one-object case is annoying, but I do want to note this; I think mentioning the data in the generated docs is sufficient though.