Upgrade tough-cookie and semver (#619)

[ps48]

Description

Upgrade tough-cookie and semver

Issues Resolved

• Upgrade tough-cookie to fix CVE-2023-26136
• Add semver resolution to patch CVE-2022-25883

Check List

• New functionality includes testing.
  • All tests pass, including unit test, integration test and doctest
• New functionality has been documented.
  • New functionality has javadoc added
  • New functionality has user manual doc added
• 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.

[joshuali925]

why is this from cve-tough-cookie branch?

[rupal-bq]

why is this from cve-tough-cookie branch?

I created it by mistake in earlier PR

[codecov]

Codecov Report

Merging #627 (c730507) into main (14ec857) will increase coverage by 0.43%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #627      +/-   ##
==========================================
+ Coverage   43.42%   43.86%   +0.43%     
==========================================
  Files         300      313      +13     
  Lines       18113    18677     +564     
  Branches     4447     4504      +57     
==========================================
+ Hits         7866     8192     +326     
- Misses       9712    10443     +731     
+ Partials      535       42     -493     

Flag	Coverage Δ
dashboards-observability	43.86% <ø> (+0.43%)	⬆️

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

see 92 files with indirect coverage changes

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 1

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
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-627-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e1a5465615bbb0f5d37369f34b9e94681842166d
# Push it to GitHub
git push --set-upstream origin backport/backport-627-to-2.x
# Go back to the original working tree
cd ../..
# 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-627-to-2.x.

[opensearch-trigger-bot]

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

Then, create a pull request where the base branch is 2.9 and the compare/head branch is backport/backport-627-to-2.9.