Security Fix for Lucene-core PRISMA-2021-0081

[imsayari404]

Description

Security fix for Lucene-core
Fixed - 1 High
vulnerable version : 8.2.0
Fixed version : 8.10.0
excluded the higher version because local source build was breaking.

Motivation and Context

Reasons to exclude:

1. Apache Lucene is vulnerable to ReDos, the regex engine in Lucene can take long time and high CPU usage before
   determining the total count for the states of a regex.

Impact

Image scan showed the vulnerability has been removed
Image scan report :
correlation-report-ibm-lh-presto lucene 10th.csv

Test Plan

Tested in 3 form factor : Cpd,Dev and SaaS

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

General Changes
* ... :pr:`12345`
* ... :pr:`12345`

Hive Connector Changes
* ... :pr:`12345`
* ... :pr:`12345`

If release note is NOT required, use:

== NO RELEASE NOTE ==

[linux-foundation-easycla]

• ❌ The email address for the commit (9947dab) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[elharo]

Thanks, please sign the CLA