Bump org.json dependency version

[dai-chen]

Description

1. Bumped org.json version in all submodules for CVE fix
2. Fixed failed UT and IT assertion due to breaking changes in Change the underflying storage for floating point numbers to BigDecimal stleary/JSON-java#441 (more details below)

Impact on UT/IT

org.json use BigDecimal to interpret floating point text in JSON. This caused the return value of JSONObject/JSONArray.get() and query() get changed from double to BigDecimal class.

Impact on User Interface

Minor changes I noticed in our response format which seems an improvement:

Previously:

POST _plugins/_sql
{
  "query": "SELECT 123.0"
}

{
  "schema": [
    {
      "name": "123.0",
      "type": "double"
    }
  ],
  "datarows": [
    [
      123  <-- the decimal part was missing
    ]
  ],
  "total": 1,
  "size": 1,
  "status": 200
}

Now:

curl -XPOST 'http://localhost:9200/_plugins/_sql' \
--header 'Content-Type: application/json' \
--data '{
  "query": "select 123.0"
}
'

{
  "schema": [
    {
      "name": "123.0",
      "type": "double"
    }
  ],
  "datarows": [
    [
      123.0  <-- exact the same as what user provided
    ]
  ],
  "total": 1,
  "size": 1,
  "status": 200
}

Issues Resolved

CVE-2022-45688

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.

[codecov-commenter]

Codecov Report

Merging #1586 (cc43408) into 2.7 (6cfe354) will not change coverage.
The diff coverage is n/a.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@            Coverage Diff            @@
##                2.7    #1586   +/-   ##
=========================================
  Coverage     97.18%   97.18%           
  Complexity     4104     4104           
=========================================
  Files           371      371           
  Lines         10459    10459           
  Branches        706      706           
=========================================
  Hits          10165    10165           
  Misses          287      287           
  Partials          7        7           

Flag	Coverage Δ
sql-engine	97.18% <ø> (ø)

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:

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

[opensearch-trigger-bot]

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

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

[opensearch-trigger-bot]

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

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