API structure rework

[skylardarkfox]

In the interest of preventing inadvertent schema exposure, and to possibly simplify the process of building out an API using this framework, the framework will be redesigned with the following requirements:

• The API will have a single controller script, regardless of how complex of a structure the user builds.
• The /?q= URL syntax will be removed in favor of virtual paths.
• These paths will be parsed by .htaccess files. (This does mean that in this form, nginx would not be supported, but perhaps there's another way to handle virtual paths.)
• The API will still use a POSTed JSON format, in the same structure as before.

[skylardarkfox]

There are use-cases to justify both a Model-based CRUD approach to API calls and a more traditional request/response approach, so it may be helpful to provide both options. The latter would probably be more likely to make use of oneShot() query calls.