fix(database/migration_runner): add check_same_thread=False to get_current_revision() SQLite engine

MigrationRunner.get_current_revision() was creating a SQLite engine without
connect_args={'check_same_thread': False}, causing ProgrammingError when called
from a different thread than the one that created the engine. This is now
consistent with init_or_upgrade() which correctly passes check_same_thread=False
for all SQLite engines.

Added a Behave scenario to verify that get_current_revision() passes
check_same_thread=False when creating a SQLite engine.

ISSUES CLOSED: #10952

features/consolidated_misc.feature

@@ -1714,6 +1714,12 @@ Feature: Consolidated Misc
     And the temporary connection should be closed afterward
 
 
+  Scenario: get_current_revision uses check_same_thread=False for SQLite engines
+    Given a migration runner configured for "sqlite:///:memory:"
+    When I request the current revision from the database
+    Then the SQLite engine for get_current_revision should use check_same_thread=False
+
+
   Scenario: File-based SQLite database directory is created if missing
     Given a migration runner configured for "sqlite:///tmp/test-db/mydb.db"
     When I initialize or upgrade a file-based SQLite database