Refactor database engine fixtures to ensure proper disposal

- Updated the `db_engine_one` and `db_engine_two` fixtures in `base.py` to use a context manager for engine disposal, ensuring that resources are properly released after use.
- Modified the `sqlite_db_engine_one` and `sqlite_db_engine_two` fixtures in `test_comparer.py` similarly to enhance resource management during tests.

Author: gianchub

tests/base.py

@@ -27,11 +27,19 @@ def db_uri_two(self, make_postgres_uri, db_name_two):
 
     @pytest.fixture
     def db_engine_one(self, db_uri_one):
-        return get_engine(db_uri_one)
+        engine = get_engine(db_uri_one)
+        try:
+            yield engine
+        finally:
+            engine.dispose()
 
     @pytest.fixture
     def db_engine_two(self, db_uri_two):
-        return get_engine(db_uri_two)
+        engine = get_engine(db_uri_two)
+        try:
+            yield engine
+        finally:
+            engine.dispose()
 
     @pytest.fixture
     def setup_db_one(self, db_uri_one, db_engine_one):

tests/test_comparer.py

@@ -205,11 +205,19 @@ def test_compare(self, db_engine_one, db_engine_two, compare_result_v14, compare
 class TestComparerSqlite(BaseTest):
     @pytest.fixture
     def sqlite_db_engine_one(self):
-        return get_engine("sqlite:///:memory:")
+        engine = get_engine("sqlite:///:memory:")
+        try:
+            yield engine
+        finally:
+            engine.dispose()
 
     @pytest.fixture
     def sqlite_db_engine_two(self):
-        return get_engine("sqlite:///:memory:")
+        engine = get_engine("sqlite:///:memory:")
+        try:
+            yield engine
+        finally:
+            engine.dispose()
 
     @pytest.fixture()
     def setup_db_one(self, sqlite_db_engine_one):