Introduce 3.0 undefine behaviour steps. Add more steps for define, redefine, match value, match as

[farost]

Usage and product changes

We update all the existing undefine tests to use the new 3.0 undefine queries, add new steps to test new 3.0 functionality (new annotations, specific errors returned for query safety), and remove some of the excessive tests (mostly non-implemented ones) for cases already covered in concept BDDs.

Additionally, we cover the missing cases for match queries:

• transitive owns/plays/relates;
• value;
• as.

Implementation

Several todos are left for match queries that should verify that the un/re/-definitions are successful, but are not implemented in 3.0 for now. Unique kinds of these TODOs are highlighted by comments of this PR.

[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.

[farost]

@dmitrii-ubskii I added more define and match tests in this PR as everything becomes connected. Please, check the newest commits!