💥Remove implicit controllers

[Robdel12]

What is this?

When integrating with the example app, it appears the implicit controller will never work. In order to call client functions / eval outside of test, you have to pass an instance of the controller.

eval cannot implicitly resolve the test run in context of which it should be executed. 
If you need to call eval from the Node.js API callback, pass the test controller manually via eval’s .with({ boundTestRun: t }) method first. 
*Note that you cannot execute eval outside the test code*

Knowing that, we have to drop that feature. Thankfully it only ever lived on the beta channels (and didn't work anyways). Along those lines, we have to use ClientFunction because eval is only available inside of test. (ClientFunction is what eval uses anyways).

[wwilsman]

🎮