Problem: mocking DB on tests is non intuitive, inconsistent a repetitive

[outerlook]

context: #128 (comment)

Maybe would be good to provide a framework for consistent usage of mocks on tests instead of relying on 1-time solutions for each test that needs to mock DB, etc.

(open for suggestion on better titles)

[MicBun]

Related for this issue #120

Maybe would be good to provide a framework for consistent usage of mocks

Since we are already free from kwil's old code, we are open to frameworks.
Here's what I usually used before my past experiences and some hobby projects:

Mock Generator: https://github.com/vektra/mockery
Mocks interface default option is mostly enough.
GORM: https://github.com/go-gorm/gorm
Boost productivity at a cost of a little bit of performance (since native sql's is always the fastest). Tables, column names, and associations around multiple features and/or files are a nightmare to maintain, might want to consider using ORM once our scope is getting bigger for friendlies.