Improve multiline query support (#284)

## Usage and product changes

We improve multi-line query support to allow copy-pasting queries and
scripts containing empty newlines. In particular this makes pasting
entire schema definitions from files.

For example, pasting a console script opening a transaction, defining a
schema containing newlines, and committing, is now possible:
```
>> transaction schema test
    define 
      entity person;  # newlines are allowed in pasted scripts:
       
      attribute name, value string;
      
      person owns name; 
   
    commit
```

Empty newlines when written _interactively_ still cause queries to be
submitted. However, an explicit query `end;` clause is a valid
alternative now:

```
>> transaction schema test
    define 
      entity person;  # newlines are allowed in pasted scripts:
       
      attribute name, value string;
      
      person owns name; 
    end; # <--- will submit immediately
```

Pasted query pipelines may now be ambiguous, such as the following
example which by defaults executs a single "match-insert" query, even
though there are newlines:
```
> transaction schema test
  match $x isa person;

  insert $y isa person;

  commit
```

To make this a "match" query and a separate "insert" query, we must use
the `end;` markers:
```
> transaction schema test
  match $x isa person;
  end;

  insert $y isa person;
  end;

  commit
```

**Note that now `end` is a reserved keyword and cannot be used as a
type!**

## Implementation

Queries are now parsed using TypeQL when given input. A "maximum" query
is parsed from the input at a time, so multi-query copy-paste and
scripts need to take care to be include the right terminators between
queries (eg "end;").

Author: flyingsilverfin

BUILD

@@ -22,6 +22,7 @@ rust_binary(
     srcs = glob(["src/**/*.rs"]),
     deps = [
         "@typedb_driver//rust:typedb_driver",
+        "@typeql//rust:typeql",
 
         # External dependencies
         "@crates//:clap",
@@ -143,6 +144,7 @@ release_validate_deps(
     refs = "@typedb_console_workspace_refs//:refs.json",
     tagged_deps = [
         "@typedb_driver",
+        "@typeql",
     ],
     tags = ["manual"], # in order for bazel test //... to not fail
     version_file = "VERSION",

Cargo.lock

@@ -38,6 +38,12 @@ features = {}
 		version = "0.3.2"
 		default-features = false
 
+	[dependencies.typeql]
+		features = []
+		rev = "7cbb621200f10f2cb741b57e82494ff9659813c6"
+		git = "https://github.com/typedb/typeql"
+		default-features = false
+
 	[dependencies.typedb-driver]
 		features = []
 		git = "https://github.com/typedb/typedb-driver"

Cargo.toml

@@ -96,7 +96,7 @@ will also be autocompleted, while others, such as queries, will not.
 
 ### Transaction-level commands
 
-- `<query>` : Once you're in the transaction REPL, the terminal immediately accepts a multi-line TypeQL query, and will execute it when you **hit enter twice**.
+- `<query>` : Once you're in the transaction REPL, the terminal immediately accepts a multi-line TypeQL query, and will execute it when you **hit enter twice (submit an empty newline) or use an explicit "end;" stage**.
   ```
   my-typedb-database::schema>> define
                               attribute name, value string;
@@ -105,7 +105,7 @@ will also be autocompleted, while others, such as queries, will not.
   Finished schema query.
   >>
   ```
-- `source <file>` : Run TypeQL queries in a file (_not a general console script_), which you can refer to using relative or absolute path. Queries must be terminated by an empty newline.
+- `source <file>` : Run TypeQL queries in a file (_not a general console script_), which you can refer to using relative or absolute path. Queries must be terminated by an empty newline or an explicit "end;" stage.
   ```
   my-typedb-database::schema> source ./schema.tql
   Successfully executed 1 queries.
@@ -183,6 +183,31 @@ Finished. Total answers: 1
 Transaction closed
 ```
 
+Queries will be parsed maximally and newlines **are** allowed.
+If you wish to split a query pipeline into two queries, or skip the usual empty newline after a query,
+use the query "end;" marker:
+```
+>> database create test
+transaction schema test
+    define 
+      entity person;  # newlines are allowed in pasted scripts:
+       
+      attribute name, value string;
+      
+      person owns name; 
+   
+    commit
+transaction write test
+    insert 
+      $x isa person;
+      
+      $x has name "bob";
+    end; # this is required to avoid creating a single "insert-match" query pipeline!
+    
+    match $x isa person, has name "bob";  # this is treated as a new query
+    
+    commit
+```
 
 ### Non-interactive modes
 
@@ -191,7 +216,9 @@ Transaction closed
 We can define a script file that contains the list of commands to run, then invoke console with `./typedb console --script=<path>`. 
 
 Script files take exactly the same format as scripts pasted directly in the REPL.
-Importantly, this means that the **end of a query is delimited by an empty newline**.
+Importantly, this means that:
+- **Ambiguous query pipelines may need to be split explicitly up with an "end;" marker**.
+- **A query is that is not ended with the "end;" marker must still be terminated with an empty newline**
 
 For example, a script `commands.tqls`
 ```