Fix CVEs about h2database

[ShahimSharafudeen]

Description

Fixes CVE-2022-23221 , CVE-2021-23463 and CVE-2021-42392 on com.h2database:h2.

Motivation and Context

Resolve a new CVE.

Impact

Should have no known impact to other code.

Test Plan

Regular PR GitHub actions

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.

== NO RELEASE NOTE ==

[steveburnett]

Consider a release note entry like the following:

== RELEASE NOTES ==

Security Changes
* Upgrade h2database to 2.2.220 in response to `CVE-2022-23221 <https://github.com/advisories/GHSA-45hx-wfhj-473x>`_, `CVE-2021-23463 <https://github.com/advisories/GHSA-7rpj-hg47-cx62>`_, and `CVE-2021-42392 <https://github.com/advisories/GHSA-h376-j262-vhq6>`_.  :pr:`24001`

[pratyakshsharma]

Let us know if you were able to figure out the root cause of the issue we discussed internally.

[ShahimSharafudeen]

Ya I found the issue. H2db version 1.4.200 only support the start date from "1890-09-30". If i am give above that this date then test cases will pass.
Reference link : h2database/h2database#2261
Currently i am trying to upgrade the version as 2.2.220, which has no vulnerabilities.

[pratyakshsharma]

Good find. :D

[pratyakshsharma]

Hi @ShahimSharafudeen is this PR ready for review now? If so, please mark it as ready for review.

[ShahimSharafudeen]

Hi @ShahimSharafudeen is this PR ready for review now? If so, please mark it as ready for review.

No. One more test failure scenario also needs to fix.