TypeDB 3.0: drop Concept API in favor of enhanced TypeQL

[flyingsilverfin]

Problem to Solve

The maintanance and extension surface area of drivers' Concept API is extremely high while the its usage is extremely low, now that TypeQL fetch handles optionality for most users. However, there is still some functionality in the Concept API that is not available in TypeQL, such as renaming types.

Proposed Solution

We should tabulate the delta between Concept API features and TypeQL expressivity, and enhance the language to cover all the remaining features that are not otherwise available.

To make sure we can migrate names in a backwards compatible/easy way, we may need to introduce type label aliases as well.

Non-final syntax:

# Idempotent rename and alias schema operations
define
  rename my_old_type my_new_type;
  # unsure if required: alias some_long_type_name some_nickname; 

[brettforbes]

Oh damn, now thats a massive rewrite for us. Its not that we weren't going to do it anyway, its just that we dont have the bandwidth at the moment. We wont be able to go to v3.0 for some time now.

It would be better if you left that to version 3.1