Test docs content in CI using antora (#1010)

## Goal
Introduce an antora playbook for testing . Any pages from external modules which are referenced are mocked.

## Implementation
* Move the code testing from `test` to `test/code`
* Introduces the antora playbook file
* Creates the `mock` folder. 
* Fixes any errors found along the way.

Author: krishnangovindraj

.factory/automation.yml

@@ -6,6 +6,12 @@ config:
 build:
   correctness:
 
+    test-docs-content:
+      image: typedb-ubuntu-22.04
+      type: foreground
+      command: |
+        npx antora generate test/content/antora-playbook-mock-for-ci.yml
+
     test-code-testing-framework:
       image: typedb-ubuntu-22.04
       type: foreground
@@ -16,15 +22,15 @@ build:
         # Note: Rust runners install their own dependencies
         sudo apt-get update
         sudo apt-get install -y python3-pip
-        python3 -m pip install -r test/runners/python_requirements.txt
+        python3 -m pip install -r test/code/runners/python_requirements.txt
         
         test/start-community-server.sh
         
         FAILED=false
-        python3 -m test.main python test/tests/python_test.adoc || FAILED=true
-        python3 -m test.main rust test/tests/rust_test.adoc || FAILED=true
-        python3 -m test.main typeql test/tests/tql_test_linear.adoc || FAILED=true
-        # python3 -m test.main typeql test/tests/tql_test_custom.adoc || FAILED=true
+        python3 -m test.code.main python test/code/tests/python_test.adoc || FAILED=true
+        python3 -m test.code.main rust test/code/tests/rust_test.adoc || FAILED=true
+        python3 -m test.code.main typeql test/code/tests/tql_test_linear.adoc || FAILED=true
+        # python3 -m test.code.main typeql test/code/tests/tql_test_custom.adoc || FAILED=true
         test/stop-community-server.sh 
         $FAILED && exit 1
         
@@ -39,7 +45,7 @@ build:
         # Note: Rust runners install their own dependencies
         sudo apt-get update
         sudo apt-get install -y python3-pip
-        python3 -m pip install -r test/runners/python_requirements.txt
+        python3 -m pip install -r test/code/runners/python_requirements.txt
         
         test/start-community-server.sh
         
@@ -51,7 +57,7 @@ build:
         FAILED=false
         for TEST_LANG in "${TEST_LANGS[@]}"; do
           for TEST_DIR in "${TEST_DIRS[@]}"; do
-            python3 -m test.main "$TEST_LANG" "$TEST_DIR" || FAILED=true
+            python3 -m test.code.main "$TEST_LANG" "$TEST_DIR" || FAILED=true
           done
         done
         test/stop-community-server.sh

academy/modules/ROOT/pages/5-defining-schemas/index.adoc

@@ -44,8 +44,8 @@ Learn about how types and functions are validated against the schema.
 --
 
 == Running examples
-
-The sample database already has the complete bookstore schema defined and data inserted. If you would like to try running the Define queries featured in the examples and exercises in this section, then you should do so using another database. To create a new database, use the *database manager* image:{page-version}@home::studio-icons/svg/studio_dbs.svg[width=24]. After creation, make sure to switch over to it using the *database selector*. For more information on how to manage databases using TypeDB Studio, refer back to xref:{page-version}@academy::2-environment-setup/2.2-using-typedb-studio.adoc[Lesson 2.2]
+// There used to be a Lesson 2.2 on how to use studio. Until we have that, I'm linking out to the studio docs.
+The sample database already has the complete bookstore schema defined and data inserted. If you would like to try running the Define queries featured in the examples and exercises in this section, then you should do so using another database. To create a new database, use the *database manager* image:{page-version}@home::studio-icons/svg/studio_dbs.svg[width=24]. After creation, make sure to switch over to it using the *database selector*. For more information on how to manage databases using TypeDB Studio, refer back to the xref:{page-version}@tools::studio.adoc[TypeDB studio reference].
 
 To run a Define query, make sure to use a *schema* session and *write* transaction. After running a Define query, you should see any committed changes to the schema reflected in the *type browser*. The examples and exercises featured in this lesson are annotated with one of the following instructions to indicate how they should be run.
 

academy/modules/ROOT/pages/5-defining-schemas/summary.adoc

@@ -121,7 +121,7 @@ Learn how to build applications on TypeDB, covering database management, transac
 Learn how to build query patterns utilising advanced elements of TypeQL syntax, and how queries are resolved by TypeDB.
 ****
 
-.xref:{page-version}@manual::defining/index.adoc[Manual: Defining schemas]
+.xref:{page-version}@typeql-reference::schema/index.adoc[Reference: Defining schemas]
 [.clickable]
 ****
 Learn more about defining schemas for TypeDB, covering Define queries, Undefine queries, and schema editing.

academy/modules/ROOT/pages/7-understanding-query-patterns/summary.adoc

@@ -125,7 +125,7 @@ Learn how to structure query results in the optimal manner, covering result grou
 Learn how to design schemas for TypeDB using the conceptual PERA model, including common design patterns and pitfalls.
 ****
 
-.xref:{page-version}@typeql::patterns/index.adoc[Reference: Patterns]
+.xref:{page-version}@typeql-reference::patterns/index.adoc[Reference: Patterns]
 [.clickable]
 ****
 Read the TypeQL patterns reference, covering conjunctions, disjunctions, negations, and pattern matching behaviour.

academy/modules/ROOT/pages/9-modeling-schemas/summary.adoc

@@ -49,7 +49,7 @@ image::academy::typeql-terminology.png[role=framed, width = 75%, link=self]
 * A simple contract can be created by making a type abstract, and implementing abstract interfaces
 * Contact us if you're interested in 'strict' contracts
 
-== xref:{page-version}@academy::9-modeling-schemas/9.9-specializations.adoc[Specialization]
+== xref:{page-version}@academy::9-modeling-schemas/9.9-specialization.adoc[Specialization]
 
 * Redeclaring schema definitions is normally disallowed - unless adding specializing annotations to them
 * Combine abstract interface implementations with interface specialization to model complex connectivity requirements

core-concepts/modules/ROOT/pages/typeql/query-variables-patterns.adoc

@@ -376,7 +376,7 @@ Such patterns are considered invalid and will throw disjoint variable usage erro
 See the xref:core-concepts::typeql/invalid-patterns.adoc[invalid patterns] page for more examples.
 
 ==== Valid variable scopes:
-Rephrasing the xref:reference::typeql/patterns/index.adoc#_scopes[unique scope principle], a variable is either:
+Rephrasing the xref:{page-version}@typeql-reference::patterns/index.adoc#_scopes[unique scope principle], a variable is either:
 
 1. Internal to one branch of one disjunction.
 2. Internal to one negation.

core-concepts/modules/ROOT/pages/typeql/sql-vs-typeql.adoc

@@ -769,7 +769,7 @@ define
 | `LIMIT` | `limit` | Identical
 | `OFFSET` | `offset` | Identical
 | `DISTINCT` | `distinct` | Identical
-| `COUNT`/`SUM`/`AVG`/`etc.` | `reduce` with `count`/`sum`/`mean`/etc. | Similar, assigned to a variable| 
+| `COUNT`/`SUM`/`AVG`/`etc.` | `reduce` with `count`/`sum`/`mean`/etc. | Similar, assigned to a variable
 | `UNION` | `or` patterns | Pattern disjunction
 | `EXISTS` | `not { not { ... } }` | Double negation pattern
 | `IN` | `or` with multiple `==` | Pattern disjunction

test/__init__.py

@@ -1 +0,0 @@
-#

test/README.md test/code/README.mdtest/README.md renamed to test/code/README.md

@@ -83,20 +83,20 @@ See examples in `./tests/` for how to write testable examples in `.adoc` files.
 ### Directory run
 
 ```bash
-python -m test.main <lang> <directory>
+python -m test.code.main <lang> <directory>
 ```
 
 ### Single file run
 
 ```bash
-python -m test.main <lang> <file>    
+python -m test.code.main <lang> <file>    
 ```
 
 ## Development
 
 ### Type checking
 
-Type check with `mypy test/main.py` (need to install `mypy`)
+Type check with `mypy test/code/main.py` (need to install `mypy`)
 
 ### Modules