3.0 Implement Driver fetch steps (#305)

## Usage and product changes
We add new behaviour tests steps to test fetch responses (concept
documents) received by the TypeDB drivers.

Additionally, we refactor some of the already existing steps to align
with the Java driver's implementation, and cover additional API's missed
before.

---------

Co-authored-by: Dmitrii Ubskii <[email protected]>

Author: farost

connection/database.feature

@@ -21,7 +21,6 @@ Feature: Connection Database
       | cAn-be_Like-that_WITH-a_pretty-looooooooooooong_name-and·even‿a·smile |
       | 資料庫                                                                   |
 
-
   Scenario: create many databases
     When connection create databases:
       | alice   |
@@ -62,6 +61,10 @@ Feature: Connection Database
     Then connection create database: !; fails
     Then connection create database: ...; fails
     Then connection create database: ·‿·; fails
+
+    # TODO: Merge it with the regular "cannot create database with an incorrect name" after fixing https://github.com/typedb/typedb-driver/issues/699
+  @ignore-typedb-driver-java
+  Scenario: cannot create database with an emoji in its name
     Then connection create database: 😎; fails
     Then connection create database: my😎database; fails
 
@@ -149,4 +152,3 @@ Feature: Connection Database
     Then transaction commits
     Then connection delete database: typedb
     Then connection does not have database: typedb
-