Adjust precision of mapped datatype for ScalarDB BIGINT on Oracle

[Torch3333]

Description

ScalarDB BIGINT is mapped to Oracle's NUMBER(19) type. However, a lower precision of 16 digits is enough to accommodate the allowed maximum value 9007199254740992L and minimum value -9007199254740992L.

Related issues and/or PRs

N/A

Changes made

Change mapping of BIGINT datatype to Oracle NUMBER(16)

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• I have considered whether similar issues could occur in other products, components, or modules if this PR is for bug fixes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• Tests (unit, integration, etc.) have been added for the changes.
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

Provide any additional information or notes that may be relevant to the reviewers or stakeholders.

Release notes

ScalarDB BIGINT datatype will now be mapped to Oracle's NUMBER(16).

[brfrn169]

LGTM! Thank you!

[komamitsu]

LGTM! 👍

[feeblefakie]

LGTM! Thank you!