feat!: lua bindings mostly for creature

[AluminumAlman]

Purpose of change

Building on top of #2216 to extend Lua bindings, a whole bunch of functions for creature, character, avatar and NPC are now exposed to Lua, with other bindings in order for the aforementioned bindings to work, and a few other miscellaneous bindings.

Describe the solution

In order to bind most of the creature class family's methods and members to Lua, the types used/returned were bound to Lua, which required refactoring/changes/additions, most of which were covered by the project's Lua documentation. Still, I had to do more than what the documentation had, and so I added those things to the documentation.
To make binding less tiresome, preprocessor macros were created to help. Though binding large classes like those of the creature family still looked threatening, and for that I used my editor's (Neovim) regex functionality to produce most of the bindings, which I outlined in the changed Lua documentation.
A enum_conversions.cpp file was created for enum_to_string<...>s needed for Lua bindings.

Testing

• Project builds on my machine;
• All tests green on my machine;
• Ran some bound functions through the Lua console to make sure that they worked;
• Changed global Lua api tests, added units (energy, angle, mass, volume) tests;
• Current tests may be lacking (e. g. no creature class family tests);
• The removed Lua global API binding for getting the avatar name did not appear in any of mods prepackaged with the project.

Additional context

• Remake of feat!: Additional Lua bindings, documentation, attitude decoupled from creature #3990;
• Additional images:
  
  
  
  

[autofix-ci]

The Autofix app has found code style violation and automatically formatted this Pull Request.

I locally edit my commits (e.g: git, github desktop)

Please choose following options:

I'd like to accept the automated commit

1. Run git pull. this will merge the automated commit into your local copy of the PR branch.
2. Continue working.

I do not want the automated commit

1. Format your code locally, then commit it.
2. Run git push --force to force push your branch. This will overwrite the automated commit on remote with your local one.
3. Continue working.

If you don't do this, your following commits will be based on the old commit, and cause MERGE CONFLICT.

This PR is complete and I don't want to edit it anymore

It's safe to ignore this message.

I edit this PR through web UI

You can ignore this message and continue working.

I have no idea what this message is talking about

You can ignore this message and continue working. If you find any problem, please ask for help and ping @scarf005.

[scarf005]

Haven't playtested yet, but looks good and tests pass.

[scarf005]

let's see how it goes.