Refactor tasks to use ListArtifact as input

[collindutter]

Several Tasks have non-BaseArtifact input fields. For instance, ImageQueryTask.input has a type of:

tuple[TextArtifact, list[ImageArtifact]]

The complexity of this type makes it very difficult to serialize the inputs of these Tasks in downstream abstractions like Events. Additionally, it make the Task API inconsistent across Task types.

This PR changes the input type to ListArtifact, making it consistent with other Task types. Note that the setter for the field is mostly unchanged, only the getter has changed.

[codecov]

Codecov Report

Attention: Patch coverage is 93.22034% with 4 lines in your changes are missing coverage. Please review.

Files	Patch %	Lines
griptape/tasks/base_task.py	0.00%	0 Missing and 1 partial ⚠️
griptape/tasks/inpainting_image_generation_task.py	90.90%	0 Missing and 1 partial ⚠️
...riptape/tasks/outpainting_image_generation_task.py	90.90%	0 Missing and 1 partial ⚠️
griptape/tasks/variation_image_generation_task.py	90.00%	0 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

[andrewfrench]

Two tiny comments, very cool to be able to support this change and not worry about breaking interfaces for users!

[andrewfrench]

My one consideration was whether or not it's useful to accept a ListArtifact here directly, similarly to how the Callable now just returns a ListArtifact. I don't think I've run into a situation where this would have made anything more convenient, and these input type unions are already unwieldy enough, but curious what you think.

[andrewfrench]

This quietly drops non-image inputs, should we raise an exception if self.input.value[1:] aren't all ImageArtifacts like in the in/outpainting tasks?

[collindutter]

@andrewfrench thanks for the review, just fixed both of your comments.