feat: Use engine support

[ptiurin]

FIR-30151

Support decoupling of databases and engines (USE DATABASE, USE ENGINES).

Design decisions:

• Connection object holds initial database/engine that's specified by the user. All cursors created from it inherit these, but also keep them local. This means that cursors change on execution of "USE DATABASE/ENGINE" where they're connected to, but any new cursors from a connection will start from the initial configuration.
• init_parameters in connection used for parameters that server side returns from USE command. On connect() we execute these queries on system engine if the user supplied database/engine and pass the resulting parameters to the Connection constructor. This ensures connection is initialised as per user parameters.
• ENGINE_STATUS is now a list, since engines V2 and engines V1 statuses are different.
• Common properties (database) in cursor moved to the base class, since they're used in both cursor versions.
• Response header parsing is refactored to a base class since it's common for sync and async.

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
83.5% Coverage on New Code
1.9% Duplication on New Code

See analysis details on SonarCloud