Inject namedWriteableRegistry during ser/deser of SearchMonitorAction

[ohltyler]

Description of changes:
When calling the transport action from another plugin with a separate classloader, the casting will fail and it will hit recreateObject fn to perform serialization/deserialization of the request. During deserialization, without converting the StreamInput to NamedWriteableAwareStreamInput, this was causing failures. This PR adds the NamedWriteableRegistry as part of the transport action constructor and in execute() in order to resolve this.

Stack trace seen (example coming from skills plugin which is calling this transport action via common-utils AlertingPluginInterface.searchMonitors():

»  java.lang.UnsupportedOperationException: can't read named writeable from StreamInput
»       at org.opensearch.core.common.io.stream.StreamInput.readNamedWriteable(StreamInput.java:1122) ~[opensearch-core-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT]
»       at org.opensearch.core.common.io.stream.StreamInput.readOptionalNamedWriteable(StreamInput.java:1149) ~[opensearch-core-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT]
»       at org.opensearch.search.builder.SearchSourceBuilder.<init>(SearchSourceBuilder.java:240) ~[opensearch-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT]
»       at org.opensearch.core.common.io.stream.StreamInput.readOptionalWriteable(StreamInput.java:974) ~[opensearch-core-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT]
»       at org.opensearch.action.search.SearchRequest.<init>(SearchRequest.java:232) ~[opensearch-3.0.0-SNAPSHOT.jar:3.0.0-SNAPSHOT]
»       at org.opensearch.commons.alerting.action.SearchMonitorRequest.<init>(SearchMonitorRequest.kt:27) ~[?:?]
»       at org.opensearch.alerting.transport.TransportSearchMonitorAction.doExecute(TransportSearchMonitorAction.kt:58) ~[?:?]

CheckList:

• 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.

[ohltyler]

Note this codepath is only triggered at integration level, and tests are written in skills plugin to test this thoroughly, since it requires executing this action from a separate plugin with a separate classloader.

[ohltyler]

Tests passing on linux and windows. Security test failures are unrelated.

[eirsep]

have you tested this by building common utils jar and setting up local server with all the necessary plugins?

[ohltyler]

have you tested this by building common utils jar and setting up local server with all the necessary plugins?

Yes

[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/alerting/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/alerting/backport-2.x
# Create a new branch
git switch --create backport-1382-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ffc183f29bc389b5831ca78818c99f789557e440
# Push it to GitHub
git push --set-upstream origin backport-1382-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting/backport-2.x

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

[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/alerting/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/alerting/backport-2.x
# Create a new branch
git switch --create backport-1382-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ffc183f29bc389b5831ca78818c99f789557e440
# Push it to GitHub
git push --set-upstream origin backport-1382-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/alerting/backport-2.x

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