Fix for incorrect nullable setting on NOT NULL columns

[NaveenNitturu]

Description

The Information schema was returning NULLABLE as YES irrespective of what is been set actually while creating the table.
This PR will fetch the columns details (is NULLABLE ?) details based on how the table was created.

Motivation and Context

This change is essential to address a specific issue on the information schema tables. The problem revolves around the occurrence of default YES in NULLABLE field while querying the information.schema tables to get the metadata details.

Impact

Added fix to fetch the columns details (is NULLABLE ?) details based on how the table was created.

Test Plan

Tested the fix by creating a table having column with NULLABLE and NOT NULLABLE columns.
Tried querying the metadata of the table from the information schema and the details were populated correctly.
Before Fix:

After Fix:

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 ==

Information Schema

* Fix nullability of columns in information schema :pr:`23577`

[tdcmeehan]

Can you add a test for this?

[rschlussel]

Thanks for this fix! Can you add a test?

[NaveenNitturu]

Thanks for this fix! Can you add a test?

Added test, Could you please review now.

[tdcmeehan]

Looks good, please clean up commit message

Fix nullability of columns in information schema

[NaveenNitturu]

Looks good, please clean up commit message

Fix nullability of columns in information schema

The commit message has been cleaned up, Could you please review now.

[prestodb-ci]

Saved that user @NaveenNitturu is from IBM