Allow unicode TypeQL variables

[flyingsilverfin]

Usage and product changes

We update to the latest TypeQL, which supports unicode variables. This means TypeDB Console can now use unicode variables, as well as labels and string attribute values.

For example, we can use Mandarin character sets:

test::schema::write> define 人 sub entity;

Concepts have been defined

test::schema::write*> commit
Transaction changes committed
> transaction test data write
test::data::write> insert $人 isa 人; 

{ $人 iid 0x826e80017fffffffffffffff isa 人; }

answers: 1, total duration: 102 ms

test::data::write*> commit
Transaction changes committed
> transaction test data read
test::data::read> match $人 isa 人; get;

{ $人 iid 0x826e80018000000000000000 isa 人; }

answers: 1, total duration: 54 ms

Implementation

• Update to the latest dependencies
• Refactor runner artifact download to be accessed via definitions in TypeDB Driver

[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

• [x] 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.