Remove motion require

[markrickert]

This PR completely removes motion-require. It's no longer needed for the newest versions of RubyMotion.

I don't expect this to get merged because this repo is a total 👻 town, but I figured I'd send the PR anyways so anyone having the same issues I was when trying to update an app that was a few years old.

If you're having problems with this library while updating your app, use this in your gemfile:

gem 'formotion', github: 'markrickert/formotion', branch: 'remove-motion-require'

...unless this gets merged and a new version is released 😉

Fixes #250

[smtm]

Thanx Mark, this branch is a lifesaver. I used this branch to build a latest version of the gem locally and reactivate my app. I battled with startup of the rake task.

This Message appeared at app start time. I tore out my hair for hours and went down the rabbit hole of hunting "Possible cyclical dependency between", "class hierarchy. Consider revision if runtime exceptions occur around undefined symbols."...

*** Terminating app due to uncaught exception 'NameError', reason: 
../gems/formotion-1.8/lib/formotion/controller/formab: uninitialized constant Formotion::FormController (NameError)

[markrickert]

@smtm Thanks for reporting back that this helped you! Sometimes putting things out there like this never get a response so I'm glad it was useful to someone other than me!

[cmckni3]

This helped me as well update from RubyMotion 4.16 and formotion 1.7