Refactor CH Django rename the api app to __APP_NAME__ and more....

restructure the CH current application templates for new Django micro services

* rename api to __APP_NAME__ (the name provided on the command line of the CH application command)
* rename the current __APP_NAME__ to a generic name e.g. `ch_django`
* add a first migration dependency to the __APP_NAME__ migration with a dependency to the CH Django migrations (force the CH Django migration to happen first)
* create an `api` folder in the __APP_NAME__ for "direct" developers to create API's in that folder

Start by locating the current Django application templates and the CH application command that supplies __APP_NAME__. Trace how the existing api and __APP_NAME__ directories and migrations are generated. Done means the template uses the requested names, establishes the CH Django migration dependency, and creates an api folder for direct developers.

Written by the indexing model from the issue text.