CtrlrMocks: Mock Lua Classes to help with development and documenting implementation

[unityconstruct]

Just pushed up an initial commit of Mock Classes
https://github.com/unityconstruct/CtrlrMocks

• I originally just wanted Mocks for panel/comp/mod, but ran into how()/what() captures of all of the Classes/Functions so figured I'd Mock them up..
• Great for looking at API in VSCode or editor of choice
• Even better, it provides a means to make notes on which funcs are available, what they need to work and document the parameters/defs/datatypes
• By putting mock return values, one can test backend code almost in its entirety without Ctrlr.
• I did 90% of my panel backend for Sysex Dumps before attempting integration with Ctrlr

require()/return/init()

• There are some caveats to using these & developing in IDE environment, namely the require() and return statements

• I manage Ctrlr->VSCode and VSCode->Ctrlr environment switching with two Stashes: one that adds them and one that removes

• Its a bit of a hassle to switch, but the time saved by being able to develop backend with a VSCode Lua debugger intellisense, etc makes up for this many times over.

• even if one doesn't integrate these into develpment, they are still useful as a form of documentation.