Warn on accessing undefined globals/names

[SquidDev]

Now that #6 is merged, we have a decent way of determining what globals and modules are available in the current context. This should allow us to monitor global and require usages, and ensure they are consistent with what one might expect.

I'm probably envisaging two warnings here, though they can probably be done with the same linter:

• Accessing unknown global: just check that we have a global (either documented within this unit or external) with this name.
• Compatible usage: if we have such a global, ensure that our usage is compatible. For now, this can probably boil down to:
  • If this is a table, ensure we're using it as so and the key exists (if it's a string literal).
  • If this is a function, ensure we're passing in sufficient arguments.

However, it's not clear how to handle external names. We can definitely bake the standard library into illuaminate, but it might be nice to find a better way.

[SquidDev]

I've done some further work in b092e0e5a2605d8431bedf7dbba5c630ed4d0c19 and 8cc50003af3cdc420730ea1ecc4173437f93cbf1. However, the two systems really need to be merged and allow defining arbitrarily complex globals.

Currently we don't warn that string.subs is invalid, as string is simply registered as a global, rather than anything more complex.