Create API module for calling the scanpy pl module

[slobentanzer]

This issue is to create a module in the API agent that can generate function calls for the scanpy pl module.

[slobentanzer]

Today:

• realised that tools need to parameterised individually, each with its own Pydantic class
• using the bind_tools functionality to evaluate a list of methods for each call (https://python.langchain.com/docs/how_to/tool_calling/)
• created submodule for plotting module, with individual pydantic classes for each method from the pl module

Todo:

• finish adding methods from plotting module to individual pydantic classes
• add useful unit tests
• add reasonable benchmark cases for plotting

[slobentanzer]

Today:

• created several fully parameterised pydantic classes to bind to llm to do zero-shot suggestions for tool calls
• realised that increasing the number of parameters (six classes with 212 fields, see details below)

Todo:

• assess options to proceed, circumventing this technical limitation
• evaluate the extent of the limitation; how many fields can we fit, and does it also depend on the number of classes?
• evaluate feasibility of the manual or semi-automatic approach, considering the envisioned use cases

Fields in classes:

1. ScanpyPlScatterQueryParameters: 15 fields
2. ScanpyPlPcaQueryParameters: 19 fields
3. ScanpyPlTsneQueryParameters: 43 fields
4. ScanpyPlUmapQueryParameters: 47 fields
5. ScanpyPlDrawGraphQueryParameters: 43 fields
6. ScanpyPlSpatialQueryParameters: 45 fields

Total number of fields across all BaseModel classes: **212 fields**

[slobentanzer]

Another observation: if we follow the Pydantic paradigm of using title as the method name, this clashes with the plotting parameter of the same name.