Python. Fix driver.close(). Add integration tests for connection closing for both core and cloud

[farost]

Usage and product changes

We fix the issue #669, where the Python Driver didn't close the connection when calling TypeDBDriver.close().

Implementation

We needed to reverse the condition of is_open().

The main issue is the absence of tests for our drivers' connections, so we:

• add new integration tests for both core and cloud;
• create an issue for behaviour tests to cover this hole for a brighter future: Tests and steps to check if connection is open or closed typedb-behaviour#289.

[typedb-bot]

PR Review Checklist

Do not edit the content of this comment. The PR reviewer should simply update this comment by ticking each review item below, as they get completed.

---

Trivial Change

• This change is trivial and does not require a code or architecture review.

Code

• Packages, classes, and methods have a single domain of responsibility.
• Packages, classes, and methods are grouped into cohesive and consistent domain model.
• The code is canonical and the minimum required to achieve the goal.
• Modules, libraries, and APIs are easy to use, robust (foolproof and not errorprone), and tested.
• Logic and naming has clear narrative that communicates the accurate intent and responsibility of each module (e.g. method, class, etc.).
• The code is algorithmically efficient and scalable for the whole application.

Architecture

• Any required refactoring is completed, and the architecture does not introduce technical debt incidentally.
• Any required build and release automations are updated and/or implemented.
• Any new components follows a consistent style with respect to the pre-existing codebase.
• The architecture intuitively reflects the application domain, and is easy to understand.
• The architecture has a well-defined hierarchy of encapsulated components.
• The architecture is extensible and scalable.

[dmitrii-ubskii]

Looks good!