Unit Test rework & Master/Ticker update (#17912)

* Unit Test rework & Master/Ticker update

* Fixes and working unit testing

* Fixes

* Test fixes and FA update

* Fixed runtimes

* Radio subsystem

* move that glob wherever later

* ident

* CIBUILDING compile option

* Fixed runtimes

* Some changes to the workflow

* CI Split

* More split

* Pathing

* Linters and Annotators

* ci dir fix

* Missing undef fixed

* Enable grep checks

* More test conversions

* More split

* Correct file

* Removes unneeded inputs

* oop

* More dependency changes

* More conversions

* Conversion fixes

* Fixes

* Some assert fixes

* Corrects start gate

* Converted some README.dms to README.mds

* Removes duplicate proc

* Removes unused defines

* Example configs

* fix dll access viol by double calling

* Post-rebase fixes

* Cleans up names global list

* Undef restart counter

* More code/game/ cleanup

* Statpanel update

* Skybox

* add

* Fix ticker

* Roundend fix

* Persistence dependency update

* Reordering

* Reordering

* Reordering

* Initstage fix

* .

* .

* Reorder

* Reorder

* Circle

* Mobs

* Air

* Test fix

* CI Script Fix

* Configs

* More ticker stuff

* This is now in 'reboot world'

* Restart world announcements

* no glob in PreInit

* to define

* Update

* Removed old include

* Make this file normal again

* moved

* test

* shared unit testing objects

* Updates batched_spritesheets and universal_icon

* .

* job data debug

* rm that

* init order

* show us

* .

* i wonder

* .

* .

* urg

* do we not have a job ID?

* .

* rm sleep for now

* updated rust-g linux binaries

* binaries update 2

* binaries update 3

* testing something

* change that

* test something

* .

* .

* .

* locavar

* test

* move that

* .

* debug

* don't run this test

* strack trace it

* cleaner

* .

* .

* cras again

* also comment this out

* return to official rust g

* Update robot_icons.dm

* monitor the generation

* .

---------

Co-authored-by: Kashargul <144968721+Kashargul@users.noreply.github.com>

code/modules/ai/README.md

@@ -1,5 +1,4 @@
-/*
-[Summary]
+## Summary
 
 This module contains an AI implementation designed to be (at the base level) mobtype-agnostic,
 by being held inside a datum instead of being written into the mob directly. More specialized
@@ -11,7 +10,7 @@ When designing a new mob, all that is needed to give a mob an AI is to set
 its 'ai_holder_type' variable to the path of the AI that is desired.
 
 
-[Seperation]
+## Seperation
 
 In previous iterations of AI systems, the AI is generally written into the mob's code directly,
 which has some advantages, but often makes the code rigid, and also tied the speed of the AI
@@ -46,7 +45,7 @@ in the future.
 	delay, as the ai_holder might not exist yet.
 
 
-[Flow of Processing]
+## Flow of Processing
 
 Terrible visual representation here;
 AI Subsystem	-> Every 0.5s -> /datum/ai_holder/handle_tactics()	-> switch(stance)...
@@ -92,7 +91,7 @@ with each other, as opposed to having individual tick counters inside all of
 the ai_holder instances.  It should be noted that handle_tactics() is always
 called first, before handle_strategicals() every two seconds.
 
-[Process Skipping]
+## Process Skipping
 
 An ai_holder object can choose to enter a 'busy' state, or a 'sleep' state,
 in order to avoid processing.
@@ -117,7 +116,7 @@ from processing the other ai_holders until the sleep() finishes.
 Delays on the mob typically have set waitfor = FALSE, or spawn() is used.
 
 
-[Stances]
+## Stances
 
 The AI has a large number of states that it can be in, called stances.
 The AI will act in a specific way depending on which stance it is in,
@@ -138,7 +137,7 @@ module folder and are mostly self contained, however some files instead
 deal with general things that other stances may require, such as targeting
 or movement.
 
-[Interfaces]
+## Interfaces
 
 Interfaces are a concept that is used to help bridge the gap between
 the ai_holder, and its mob. Because the (base) ai_holder is explicitly
@@ -168,7 +167,7 @@ ranged attack. For simple_mobs, they can if a ranged projectile type was set,
 where as for a human mob, it could check if a gun is in a hand. For a borg,
 it could check if a gun is inside their current module.
 
-[Say List]
+## Say List
 
 A /datum/say_list is a very light datum that holds a list of strings for the
 AI to have their mob say based on certain conditions, such as when threatening
@@ -181,7 +180,7 @@ mercenaries and fake piloted mecha mobs.
 
 The say_list datum is applied to the mob itself and not held inside the AI datum.
 
-[Subtypes]
+## Subtypes
 
 Some subtypes of ai_holder are more specialized, but remain compatible with
 most mob types. There are many different subtypes that make the AI act different
@@ -196,6 +195,3 @@ To use a specific subtype on a mob, all that is needed is setting the mob's
 ai_holder_type to the subtype desired, and it will create that subtype when
 the mob is initialize()d. Switching to a subtype 'live' will require additional
 effort on the coder.
-
-
-*/