Better opcache handling

- Disable opcode caching if any of OpCache, XCache, or WinCache are
  detected.
- Creates an API endpoint for determining if an opcode cache is
  currently enabled.
Display a modal if an opcache is detected via the API

- Hit the /admin/api/cache-enabled service on page load.
- If the cache-enabled service returns true, display a modal dialog indicating
  that the user needs to disable their OpCode cache.
Rebuilt distribution
Remove obsolete ng-controller directive

- opted not to use a controller here, but forgot to remove it from the template
OpCache will have rules in zf-configuration

... that will invalidate the cache for the config files being written.
Merge branch 'feature/opcode-cache-detection'

If XCache or WinCache are detected at application initialization, disable them.

When the Admin UI loads, detect if the API is operating under an opcode cache,
and, if so, display a modal indicating this fact and how to disable the opcode
cache. In the case of OpCache, zf-configuration will invalidate the cache for
a configuration file after writing it, so the API will not indicate an opcode
cache is in effect for that particular opcode cache.