Change Details

Implemented as part of [ENG-10603](https://linear.app/comm/issue/ENG-10603/biggest-risk-factor-out-code-from-databasequeryexecutor). Currently, we have: 1. `SQLiteConnectionManager` that is used on web 2. `NativeSQLiteConnectionManager` that is inheriting from the class `SQLiteConnectionManager` and override couple methods to be native-specific. 3. `SQLiteQueryExecutor` that owns `*connectionManager` and use it but connection management is implemented in multiple places. This diff changes the approach to the following: 1. `SQLiteConnectionManager` will abstract class with pure vritual functions that depends on platform (this way, we can avoid directives in `SQLiteQueryExecutor` and put platform-specific implementation into dedicated classes). Shared code will be implemented in parent class 2. `NativeSQLiteConnectionManager` that is inheriting from the class `SQLiteConnectionManager` and override-native specific methods. 3. `WebSQLiteConnectionManager` that is inheriting from the class `SQLiteConnectionManager` and override web-specific methods. 4. `SQLiteQueryExecutor` that owns `*connectionManager` instance based on platform, but connection management will be fully moved to `*connectionManager` (later in the stack) Depends on D14573

Implemented as part of [ENG-10603](https://linear.app/comm/issue/ENG-10603/biggest-risk-factor-out-code-from-databasequeryexecutor). Currently, we have: 1. `SQLiteConnectionManager` that is used on the web 2. `NativeSQLiteConnectionManager` that is inheriting from the class `SQLiteConnectionManager` and overrides a couple of methods to be native-specific. 3. `SQLiteQueryExecutor` that owns `*connectionManager` and uses it, but connection management is implemented in multiple places. This diff changes the approach to the following: 1. `SQLiteConnectionManager` will be an abstract class with pure virtual functions that depend on the platform (this way, we can avoid directives in `SQLiteQueryExecutor` and put platform-specific implementation into dedicated classes). Shared code will be implemented in this, parent class 2. `NativeSQLiteConnectionManager` that is inheriting from the class `SQLiteConnectionManager` and overrides native-specific methods. 3. `WebSQLiteConnectionManager` that is inheriting from the class `SQLiteConnectionManager` and overrides web-specific methods. 4. `SQLiteQueryExecutor` that owns `*connectionManager` instance based on platform, but connection management will be fully moved to `*connectionManager` (later in the stack) Depends on D14573

Implemented as part of [ENG-10603](https://linear.app/comm/issue/ENG-10603/biggest-risk-factor-out-code-from-databasequeryexecutor). Currently, we have: 1. `SQLiteConnectionManager` that is used on the web 2. `NativeSQLiteConnectionManager` that is inheriting from the class `SQLiteConnectionManager` and overrides a couple of methods to be native-specific. 3. `SQLiteQueryExecutor` that owns `*connectionManager` and use ituses it, but connection management is implemented in multiple places. This diff changes the approach to the following: 1. `SQLiteConnectionManager` will be an abstract class with pure vrivirtual functions that depends on on the platform (this way, we can avoid directives in `SQLiteQueryExecutor` and put platform-specific implementation into dedicated classes). Shared code will be implemented in this, Shared code will be implemented in parent class 2. `NativeSQLiteConnectionManager` that is inheriting from the class `SQLiteConnectionManager` and override-s native -specific methods. 3. `WebSQLiteConnectionManager` that is inheriting from the class `SQLiteConnectionManager` and overrides web-specific methods. 4. `SQLiteQueryExecutor` that owns `*connectionManager` instance based on platform, but connection management will be fully moved to `*connectionManager` (later in the stack) Depends on D14573