Adding reprovision integration tests

[joshpalis]

Description

Adds integration tests for reprovision param.

Related Issues

resolves #822

Check List

• New functionality includes testing.
• New functionality has been documented.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

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

Attention: Patch coverage is 84.37500% with 5 lines in your changes missing coverage. Please review.

Project coverage is 77.47%. Comparing base (268f746) to head (558e374).
Report is 2 commits behind head on main.

Files	Patch %	Lines
...h/flowframework/rest/RestCreateWorkflowAction.java	0.00%	3 Missing and 1 partial ⚠️
...search/flowframework/workflow/UpdateIndexStep.java	94.73%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #834      +/-   ##
============================================
+ Coverage     75.38%   77.47%   +2.09%     
- Complexity      917      928      +11     
============================================
  Files            96       96              
  Lines          4456     4359      -97     
  Branches        412      413       +1     
============================================
+ Hits           3359     3377      +18     
+ Misses          925      810     -115     
  Partials        172      172              

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

[dbwiddis]

LGTM with a few suggestions.

All the resource matching lookups could probably be streamlined with a helper method producing a map.

[amitgalitz]

Can we add a test case where we reprovision a default use_case template?

[dbwiddis]

LGTM!

Approved with suggestions, feel free to take them or ignore them.

[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-834-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 562d476ae21775b9aac274757608d7eef43d9247
# Push it to GitHub
git push --set-upstream origin backport/backport-834-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-834-to-2.x.

[joshpalis]

Will raise the backport manually