feat(sqlite): SQLite Module for Hermes

[apskhem]

Description

Add integration test for Hermes SQLite module for running on WASM runner.

Related Issue(s)

Closes #246

Description of Changes

• Added integration test for the SQLite module in both functional tests and benchmarks
• Added internal state for SQLite module. Without this, will cause error during WASM runtime

Please confirm the following checks

• My code follows the style guidelines of this project
• I have performed a self-review of my 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 pass locally with my changes
• Any dependent changes have been merged and published in downstream module

[stevenj]

Can you also add preliminary results from your benchmarks, comparing the speed of the in-memory sqlite db and the on-disk one?

Add a readme to the integration-test directory with a summary of the results of the benchmark. Make sure to include details of the machine it was run on. This way we have something to compare it to if we run it somewhere else.

[Mr-Leshiy]

Seems it's time add a generalised object which will maintain wasmtime::Resources.
So this abstraction will be used in both crypto and sqllite runtime extensions.
It could be something like:

trait ResourceAllocation {
   fn allocate<T>(params: T) -> Self {
    }
}

trait ResourceDeallocation {
   fn deallocate<T>(params: T) -> Self {
    }
}

struct ResourceManager<T> {
  apps_state: DashMap<HermesAppName, DashMap<u32, wasmtime::Resources<T>>>,
}

[apskhem]

Seems it's time add a generalised object which will maintain wasmtime::Resources. So this abstraction will be used in both crypto and sqllite runtime extensions. It could be something like:

trait ResourceAllocation {
   fn allocate<T>(params: T) -> Self {
    }
}

trait ResourceDeallocation {
   fn deallocate<T>(params: T) -> Self {
    }
}

struct ResourceManager<T> {
  apps_state: DashMap<HermesAppName, DashMap<u32, wasmtime::Resources<T>>>,
}

Generalizing this is a great idea, but it might be a bit out of scope at the moment. Once the all the modules are stable, we can revisit the idea of creating traits and structs for internal generalization with a dedicated ticket. As we have state using in cron, crypto, and sqlite modules, they are really have their own way of managing and storing states.

All resolved

[stevenj]

LGTM