fix(FIR-51029): Database cache logic

[ptiurin]

This pull request addresses a bug in the Firebolt engine caching logic that previously caused incorrect database context to be used when switching databases with the same engine. The main fix ensures that the database parameter is not cached with engine information, preventing database context from being overwritten when reusing engine cache entries. The changes also add comprehensive integration and unit tests to verify correct behavior for both async and sync connections, and update test factories for better flexibility.

Bug Fixes and Engine Caching Improvements:

• Updated use_engine and use_engine_async methods to exclude the database parameter from engine cache entries, ensuring that switching databases with the same engine does not overwrite the database context. [1] [2]

Testing Enhancements:

• Added new integration and unit tests (both async and sync) to verify that switching databases with the same engine preserves the correct database context and that the engine cache does not contain the database parameter. [1] [2] [3]
• Updated connection factory fixtures in both async and sync test suites to allow dynamic selection of the database parameter, improving test flexibility and coverage. [1] [2]

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud