examples: in impls and ompls update shell.yml files

[manushak]

Types of changes

• Enhancement (project structure, spelling, grammar, formatting)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

A description of the changes proposed in the Pull Request

• made changes in shell.yml files in impls and ompls test folders

[jmcook1186]

command should be provided in the model config above, rather than in an individual input
e.g.

child:
  pipeline:
    - sampler
  config:
    sampler:
      command: python3 /usr/local/bin/sampler
  inputs:
    - timestep: "2023-11-02T10:35:31:820Z"
      energy: 1
      duration: 10

p.s. your version will run correctly in this case where there is only one timestep, but if there are multiple timesteps it will break unless you manually copy the command into each one. Putting it in the config means the value its autromaticaly copied to every input.

[manushak]

So, this PR doesn't have any sense?

[jmcook1186]

no, as long as executable is renamed to command that was the only required change to the impls

[manushak]

done

[jmcook1186]

left a comment about the position of command

[jmcook1186]

made some more small changes that I noticed, otherwise sgtm