Initial fix for apiEnableAction() and ApiProblem usage
Merge pull request #151 from zfcampus/hotfix/module-enable

Initial fix for apiEnableAction() and ApiProblem usage
Re-added PHPUnit runner

- removed accidentally with fd23e96c
[#151] Fix issue with Module entity access

- `injectModuleCollectionRelationalLinks()` was accessing the
  ModuleEntity as if it were an array. Altered to retrieve data from it
  as an array, and then to seed a new ModuleEntity when complete.
[#151] Fix failing unit tests

- Code changed to return an ApiProblemResponse, but the tests were not updated
  to reflect this.
Fix failing/erroring unit tests

- Issues were due to 1d185faca - which changed how the DbConnectedEntity
  returns the `resource_class` (in all cases where a "virtual" resource
  name is used, the value will now be `null`). Updated tests to reflect
  the change.
Ensure all relevant configuration for a REST service is deleted

- Ensure routing, content-negotiation, content-validation, hal,
  authroization, versioning, and service manager configuration is
  removed when deleting a service.
- Do **not** delete the route or versioning information if the service
  version is greater than 1.
Delete all configuration associated with an RPC service

- Removes content-validation, versioning, authorization, and controllers
  configuration for an RPC service.
- Ensures route and versioning config are **not** removed when the
  version is greater than 1.
CS fixes (trailing whitespace, function declaration)
Fix failing tests

- Since FooConf and BarConf test modules are proper Apigility modules now,
  needed to update the cleanupAsset routines to remove versioned directories
  only.
Merge branch 'hotfix/151'

Close #151
Merge pull request #150 from weierophinney/hotfix/delete-remove-all-config

Remove all config data for a service on deletion
First draft of recursive delete
Implemented logic for deleting an API

- This patch implements the logic necessary to delete an API module. If
  the "recursive" flag is sent with a value that evaluates true, then a
  recursive deletion of the module is made; otherwise, the entry for the
  module is simply removed from the application configuration.