Feature/singlestore integration tests

[Rodriguespn]

Integration Tests

Copied and renamed every mysql reference to singlestore on integration-tests directory

Key differences between MySQL vs SIngleStore IT Tests

• Renamed all references from MySQL to SingleStore in the integration tests directory.
• The tests are performed against the singlestore-dev docker image, to replicate a production environment
• SingleStore's serial column type only assures uniqueness of the column values. The tests were modified to (set operation tests in particular) to expect SingleStore-specific behavior, by adding an ORDER BY instruction to every select instruction.
• ORDER BY and LIMIT cannot be chained together.
• Removed SingleStore proxy package and its IT tests. If it's necessary, this package can be replicated from the MySQLL proxy package later
• The foreign key integration tests were removed since they are not supported by singlestore
• Removed intersectAll and exceptAll tests since these operations are not supported by SIngleStore
• Removed nested transaction tests since this feature is not supported by SingleStore
• Removed isolationLevel config and tests as singlestore only supports one isolationLevel

---

Side notes

There are some SingleStore-specific operations, such as attach/detach, create/drop milestone and optimyzeTable for column stores tables, that are implemented on drizzle-orm/src/singlestore-core but not on drizzle-kit. There are also no integration tests for these operations. This is a known issue and should be fixed in the upcoming releases.

[Rodriguespn]

@apeng-singlestore @mitchwadair @tiagoacastro @drodrigues4 is ready to be reviewed

[mitchwadair]

Cool, I'll take a look soon 👍

[apeng-singlestore]

Notable Changes

• Renamed all references from MySQL to SingleStore in the integration tests directory.
• Modified timestamp precision and other minor test adjustments
• Updated the test environment to use the SingleStore dev Docker image.

Known Issues:

• SingleStore does not order by by default, so some test expectations (set operation tests in particular) were modified to expect SingleStore-specific behavior
• ORDER BY and LIMIT cannot be chained together.
• INTERSECT ALL, EXCEPT ALL, and nested transaction operations are not supported and associated tests were removed
• Only one isolationLevel is supported, so associated tests and config options were removed

[Rodriguespn]

Thank you @apeng-singlestore. I updated the PR's description with your notable changes/known issues

[mitchwadair]

Generally LGTM, just a few comments. Very exciting!

[mitchwadair]

I also updated the main PR description with @apeng-singlestore's notes

[Rodriguespn]

I don't think this should be here after removing using method