Flesh out the selene standard library definition to improve the quality of linter warnings

[rdw-software]

The evo.yml file currently defines just enough of the standard library to fix the linter warnings. Additional lints and better feedback could be enabled if it was more detailed with its typing and allowed usage patterns, and also I'm certain it doesn't cover the entire API.

See the selene docs for some of the other available options.

---

Split off from #21 since it'll require additional work, for example creating known "bad" usage patterns for testing.

[rdw-software]

It might be helpful to store the environment in a format more suitable to processing, such as a Lua table. This could also be used to automate generating some parts of the documentation, LSP type hints and other tools - experimentally, start with globals?

The aliases can be exported quite easily, which should be enough to get started with a LSP, selene, and docusaurus.