fix(issue-2139): bigint timestamps

[design1online]

Description

This resolves the problem with using a bigint for timestamps in the database.

Related #2139

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Run the same test as provided in the issue.

Test Environment:

• OS: MacOS
• GraphQL Scalars Version: 1.22.4
• NodeJS: v18.x

Checklist:

• [] I have followed the CONTRIBUTING doc and the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests and linter rules pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[ardatan]

This breaks the support for milliseconds, and this would be a breaking change. If we kept the support for ms timestamps, that would be ok.