Add optional config field to tool step

[dbwiddis]

Description

Adds the optional config map to the ToolStep

Related Issues

Resolves #878

Draft, pending merge:

• add config field in MLToolSpec for static parameters ml-commons#2977

Check List

• New functionality includes testing.
• New functionality has been documented.
• Commits are signed per the DCO using --signoff.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.09%. Comparing base (389d680) to head (ee9e545).
Report is 1 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #899      +/-   ##
============================================
+ Coverage     78.07%   78.09%   +0.01%     
  Complexity      995      995              
============================================
  Files            99       99              
  Lines          4621     4624       +3     
  Branches        431      431              
============================================
+ Hits           3608     3611       +3     
  Misses          833      833              
  Partials        180      180              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[amitgalitz]

Looks good, but as mentioned should be merged only after ml commons PR is merged and we can then uncomment the lines in ToolStep and ToolStepTests

[joshpalis]

lgtm, approved to unblock

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/flow-framework/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/flow-framework/backport-2.x
# Create a new branch
git switch --create backport/backport-899-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 6a4bed82d6b86438762f02a1eb600cff20d9c8ca
# Push it to GitHub
git push --set-upstream origin backport/backport-899-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/flow-framework/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-899-to-2.x.