Handle exceptions for adding request body audit log if rest request is invalid

[Aayush8394]

Description

This change fixes the bug #1849. This change ensures audit logging logs a failed request if request body fails to match content-type header or required parameters.

• Category: Bug fix
• Why these changes are required?
  This change is required to be consistent with user provided configuration of audit logging request body even for failed requests
• What is the old behavior before changes and new behavior after changes?
  Before this change, an invalid request (with invalid content or source type parameters) did not get audit_request_body even if request body audit logging is enabled by user because of improper exception handling. After this change, audit_request_body will be generated

Issues Resolved

#1849

Is this a backport? If so, please add backport PR # and/or commits #

Testing

Unit tested

Check List

• New functionality includes testing
• New functionality has been documented
• 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.

[cwperks]

LGTM! Thank you @Aayush8394!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.20%. Comparing base (a5a5e03) to head (e0b5bcd).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4232      +/-   ##
==========================================
+ Coverage   66.15%   66.20%   +0.04%     
==========================================
  Files         301      301              
  Lines       21708    21710       +2     
  Branches     3506     3506              
==========================================
+ Hits        14362    14373      +11     
+ Misses       5584     5577       -7     
+ Partials     1762     1760       -2     

Files	Coverage Δ
...pensearch/security/auditlog/impl/AuditMessage.java	76.38% <100.00%> (+1.62%)	⬆️

... and 3 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:

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

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

[cwperks]

@Aayush8394 Can you create a manual backport to 2.x for this?