Frontend module reorg

This commit message describes most of this:

    Start to simplify our angular namespaces
    
    Move toward cleaning up our angular namespaces and organization. By
    flattening our namespaces and changing our file naming we're able to
    reduce the boilerplate needed for angular module and asset bundle
    definitions.
    
    - Kill all the ``h.*`` angular submodules except for ``h.auth``,
      ``h.helpers`` and ``h.identity``. This vastly reduces the amount
      of dependency repetition throughout our angular files as all
      the dependencies of the entire main h module can be declared in
      app.coffee and all the other files simply add their exports to
      the main module.
    
    - Add a helpers/helpers.coffee module definition file so that the
      rest of the helpers can use the 1-arity ``angular.module`` getter
      to attach themselves. These files can all be included with a
      glob in the asset bundle definition.
    
    - Use the glob syntax to include all the directives in the asset
      bundle definition.
    
    - Rename the controller modules in the auth bundle with a '-controller'
      suffix. These can be similarly globbed in the bundle definition.
    
    - Ensure that all controllers are named in the ``FooController`` style.


If I read this correctly, it should ensure that the `h` module is loaded.
https://docs.angularjs.org/api/ngMock/function/angular.mock.module

I think that the modules persist across test runs, but they are essentially just descriptions of providers and nothing is really instantiated until `inject` is called, at which point the modules providers are initialized and configuration functions are called.

So we're not re-registering any components by just ensuring the module is loaded. That part is idempotent. It ensures the registrations are there, but instantiates nothing.

Does that seem right?