Adds log4j configuration for telemetry-otel plugin

[Gaganjuneja]

Description

Adds log4j configuration for telemetry-otel LoggingSpanExporter. We will create our on log4j programatic appender later on to avoid the log file generation on case of LoggingSpanExporter is not configured.

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)

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.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/18892/
• CommitID: ec492e1
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/18894/
• CommitID: 3ca8950
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure a flaky test unrelated to your change?

[Gaganjuneja]

@reta @shwetathareja Please take a look. Thanks!

[reta]

@Gaganjuneja LGTM but Gradke check is failing (spotless), could you please fix that?

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.remotestore.SegmentReplicationUsingRemoteStoreIT.testNodeDropWithOngoingReplication

• URL: https://build.ci.opensearch.org/job/gradle-check/19053/
• CommitID: 8eb7939
  Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

[codecov]

Codecov Report

Merging #8393 (8eb7939) into main (d5482f7) will increase coverage by 0.13%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main    #8393      +/-   ##
============================================
+ Coverage     70.88%   71.01%   +0.13%     
- Complexity    56926    56976      +50     
============================================
  Files          4757     4757              
  Lines        269102   269109       +7     
  Branches      39396    39397       +1     
============================================
+ Hits         190746   191101     +355     
+ Misses        62284    61884     -400     
- Partials      16072    16124      +52     

Impacted Files	Coverage Δ
...pensearch/common/bytes/AbstractBytesReference.java	84.66% <100.00%> (+0.58%)	⬆️
...search/telemetry/tracing/OTelResourceProvider.java	100.00% <100.00%> (ø)

... and 465 files with indirect coverage changes

[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:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-8393-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7a5c810a238e0566f0c7bdb6fbc774dafb3674b0
# Push it to GitHub
git push --set-upstream origin backport/backport-8393-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/backport-2.x

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

[reta]

@Gaganjuneja sadly needs manual backport to 2.x :(

[Gaganjuneja]

@Gaganjuneja sadly needs manual backport to 2.x :(

Yes, will do that. Thanks!