Add support for ignoring missing Javadoc on generated code using annotation (# 7264)

[austintlee]

It can be tedious and error prone to have to specify individual source files of generated code that does not follow OpenSearch standards.

Description

Allow wildcard expressions in missingJavadoc.

Related Issues

Resolves #7264

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• [x ] Commits are signed per the DCO using --signoff
• [ x] 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/15571/
• CommitID: dcf9e4f
  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: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.remotestore.SegmentReplicationRemoteStoreIT.testReplicaHasDiffFilesThanPrimary
      1 org.opensearch.index.remote.RemoteRefreshSegmentPressureServiceTests.testValidateSegmentUploadLag

• URL: https://build.ci.opensearch.org/job/gradle-check/15573/
• CommitID: dea2058
  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 #7604 (1cba0a5) into main (adf7e2c) will increase coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #7604      +/-   ##
============================================
+ Coverage     70.72%   70.77%   +0.05%     
- Complexity    56146    56189      +43     
============================================
  Files          4682     4682              
  Lines        266102   266102              
  Branches      39070    39070              
============================================
+ Hits         188193   188339     +146     
+ Misses        61935    61832     -103     
+ Partials      15974    15931      -43     

see 440 files with indirect coverage changes

[dblock]

LGTM, is there a place you want to use this, maybe add as part of this PR? Also probably ok adding a CHANGELOG line, even if it's tools.

[dblock]

LGTM, is there a place you want to use this, maybe add as part of this PR? Also probably ok adding a CHANGELOG line, even if it's tools.

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: FAILURE ❌
• URL: https://build.ci.opensearch.org/job/gradle-check/16000/
• CommitID: 31ab340
  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?

[dblock]

Add to CHANGELOG?

We got to get gradle checks to pass on main :(

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: SUCCESS ✅
• URL: https://build.ci.opensearch.org/job/gradle-check/16373/
• CommitID: 777acc0

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.search.backpressure.SearchBackpressureIT.testSearchShardTaskCancellationWithHighCpu

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

[github-actions]

Gradle Check (Jenkins) Run Completed with:

• RESULT: UNSTABLE ❕
• TEST FAILURES:

      1 org.opensearch.search.backpressure.SearchBackpressureIT.testSearchShardTaskCancellationWithHighCpu

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

[reta]

Thanks a lot @austintlee !

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