bug: handle Optional params in schema validation

[anakin87]

Related Issues

• fixes Schema validation does not allow for null values in case of Optional typed params #2589

Proposed Changes:

First draft to manually temporarily fix this problem.
When Pydantic v2 will be released, there will be no need of this fix.

How did you test it?

Included test

Notes for the reviewer

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added tests that demonstrate the correct behavior of the change
• I've used the conventional commit convention for my PR title
• I documented my code
• I ran pre-commit hooks and fixed any issue

[anakin87]

Notes for the reviewer

In handle_optional_params function:

• I first find the optional params. This implementation is tested in Python 3.7 and 3.10, even if the annotations management is different in the two versions.
• for every optional param, the schema is updated using anyOf and {"type": "null"}.
  I don't like very much this part and I also tried to monkey patch the Pydantic schema generation, but it seemed too intricate.

The test tries to load a pipeline, with a null parameter. This test was failing with the current JSON schema.

[ZanSara]

Hello @anakin87, thank you, this issue has been standing for a good while!

I found some small occasions for improvement but the approach looks good.

[vblagoje]

Great timing @ZanSara and @anakin87 - I need this PR for #3062

[ZanSara]

Amazing, thank you! The test is 100% exactly as I had it in mind 😊