fix: Generate parameters to generated client without adding None BNCH-22940

[GitOnUp]

Upstream generates the client this way, and in a parallel benchling-sdk ticket we'll be doing a conversion to UNSET for None parameters in the service layer. Making this change in the fork in the meantime will keep us in a good state.

[GitOnUp]

William was reviewing this set of changes on the benchling-sdk side for https://github.com/benchling/benchling-sdk/pull/149, but has indicated he's about to be OOO.

[forest-benchling]

Is this just so that our switching onto the upstream is more incremental?

[GitOnUp]

@forest-benchling yes, and so that we don't continue to accidentally try to call the client functions with None in the interim period before the switch.

[forest-benchling]

@forest-benchling yes, and so that we don't continue to accidentally try to call the client functions with None in the interim period before the switch.

@GitOnUp 👍 . Just to clarify, that this is only a matter of type hinting--we're still allowing runtime calls with None, IIUC.