Add schema functionality for parameters of List[SchemaObject] NOT to be logged to new child experiments

[armaan-dhillon]

Is your enhancement request related to a problem? Please describe
We'd like to be able to define an input or output of List[SchemaObject] where SchemaObject is an object that is already represented by a schema (like a model) and NOT have Rubicon log these objects to new child experiments as described in the rubicon-ml documentation. Currently, rubicon-ml allows for schema definitions where the children key can be provided to handle lists of schema items to be logged to children experiments.

This new functionality would be in order to support lists of SchemaObjects which don't necessarily call for their own unique experiment to be logged, and would be better suited for logging to the at-hand experiment.

Describe the solution you'd like
A schema key analogous to children which allows us to define a list of List[SchemaObject] to be logged to the current experiment. Say helpers for example.

Describe alternatives you've considered

Additional context
This would be to support logging of classes that extend say a pydantic BaseModel (link to Docs) that isn't necessarily providing data that warrants its separation into a "child experiment."