Automatic ENUM globals + better windows handling

[luttje]

@robotboy655 in #41

Some considerations:

• Perhaps enum globals should be automatic somehow?

• local Weapon = {} is duplicated in the output. Not sure how to handle this, given that, at least on Windows, you cannot have the same file with different capitalization (class.WEAPON.lua and class.Weapon.lua)

IIRC I ignored the merging of class.WEAPON.lua and class.Weapon.lua, because it seemed to work fine with the VSCode Language server as is. However it would be cleaner if we prevented that duplication. Some options that come to mind:

• When refactoring how enums are automatically scraped from the wiki, placing them in a separate folder
• Hashing the file name so it's always unique (poor approach for human readability)