Write backends for documentation and lua language server formats

[makspll]

Given a standard format for declaring what function and types are available, we should be then able to generate documentation and any other file format we require

• Initial LAD format
• mdbook preprocessor
• Fine tuning the format + preprocessor
• lua declaration files backend

[Joakker]

Here's my idea

When a method is registered, you would run a method on the arg type which returns a list of the types of the arguments in the scripting language side. Stuff like FunctionContext gets skipped because it's handled by bms, but would mark the function as impure if the caller cares about it (since we likely want it to get the world). Same for the return type

An arg named self_ would correspond to the receiver, which means this is an instance function. If there is none, it's a static method.

Going one step above, namespaces would add to a global resource that contains all this metadata (namespaces/classes and their methods) since they already have access to the world

One step further, world would have a method that would generate the declaration files, passing the metadata through a function provided by the specific language plugin to make it into readable code

For example, LuaScriptingPlugin would provide a function that generates lua class/method declarations given the data generated above

[Joakker]

Sorry if it's all over the place, I'm at work writing this 🙃

[makspll]

I do like the idea of marking functions as pure or not depending on if they access the world! Ideally we'd be able to tell exactly which parts of the world they do access, maybe instead of exposing the whole world, I could just have a system param system similarly to bevy!