Added org.apache.logging.log4j:log4j-slf4j-impl to classpath

[Noir01]

Description

Fixes warning message shown when sending test message.

Issues Resolved

fix #693

Check List

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

[xluo-aws]

should we add dependency on slf4j-api instead? and use versions.slf4j instead of hard code to 1.7.32?

[Noir01]

So, instead of having implementation "org.slf4j:slf4j-jdk14:1.7.32", would it be better to have implementation "org.slf4j:slf4j-api:${versions.slf4j}"?

[xluo-aws]

Yes, please test if the warning is gone or not following the reproduce steps at #693

[gaobinlong]

By my test, this change doesn't work, the warning log still exists, please dive deep on it, thanks!

[gaobinlong]

Here are the steps about how to configure the email channel, please show the test result after the code change.

I think the main steps for test can be as follows:

1. Make some code change.
2. Build new packages for notification plugin and notification-core plugin: run ./gradlew assemble under the sub-directory notifications in the main directory of this repo.
3. Build a new package for opensearch core: run ./gradlew localDistro in the main directory of the opensearch repo, see https://github.com/opensearch-project/OpenSearch/blob/main/DEVELOPER_GUIDE.md
4. Step into the directory of the new built package of opensearch core, maybe build/distribution/local/opensearch-3.0.0-SNAPSHOT, install the new built packages of notification-core and notification plugin: ./bin/opensearch-plugin install file:///.../*.zip
5. Run OpenSearch
6. Run OpenSearch-Dashboards, need to install the notification dashboard plugin
7. Config the email sender in OpenSearch-Dashboards, refer to https://opensearch.org/docs/latest/observing-your-data/notifications/index/, here is my test sender:

8. Config keystore, set the email temporary password which is generated by Google APP password(if you use gmail): Stop OpenSearch, run `./bin/opensearch-keystore add opensearch.notifications.core.email.binlong.username`, set it to the email address, and run `./bin/opensearch-keystore add opensearch.notifications.core.email.binlong.password`, set it to the new generated password, note that `binlong` is the name of the email sender created in step 7.

9. Run OpenSearch

10. Create a channel in OpenSearch-Dashboards, choose the email sender, click Send test message ,check the main log of OpenSearch.

[Noir01]

I accidentally swapped the commit messages for the two commits I did.

[codecov]

Codecov Report

Merging #791 (2773cd5) into main (76ddcd4) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #791   +/-   ##
=========================================
  Coverage     66.85%   66.85%           
  Complexity      263      263           
=========================================
  Files            39       39           
  Lines          1738     1738           
  Branches        165      165           
=========================================
  Hits           1162     1162           
  Misses          453      453           
  Partials        123      123           

Flag	Coverage Δ
opensearch-notifications	66.85% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

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

[gaobinlong]

@Noir01 ,automatic backport to 2.x failed, could you please create a backport PR manually?