Pass arguments with command execution step in meshing workflow

```python
update_boundaries = watertight.update_boundaries(
       boundary_zone_list=["wall-inlet"],        
boundary_label_list=["wall-inlet"],        
boundary_label_type_list=["wall"],        
old_boundary_label_list=["wall-inlet"],        
old_boundary_label_type_list=["velocity-inlet"],    
)

watertight.import_geometry(
cad_import_options: {'one_zone_par': 'body'}
)
```

Something like the one given above should be allowed.

Start by tracing the meshing workflow's command execution step and compare it with the shown update_boundaries and import_geometry calls. Define the supported argument-passing behavior for these examples, then verify that the workflow accepts the demonstrated arguments and preserves existing command execution behavior.

Written by the indexing model from the issue text.