Merge pull request #220 from jguittard/master

Timeout delay upon API creation and deletion
Rebuilt UI distribution
Merge branch 'hotfix/220'

Close #220
Fixes #175
Fixes #217
[#215] subtitute dashes with namespace separators

... in controller_service_name matches
[#215] Reset matched controller service name when generating HAL links

- Added listeners to:
  - replace namespace separators in the matched controller_service_name
    with dashes
  - do the same for the controller_service_name property of REST and RPC
    entities
[#215] Working approach for handling REST/RPC entity identifiers

- Update the entity BEFORE rendering, and remove the "self" link
- During renderEntity(), re-create the "self" link based on the current
  entity
- NOT WORKING: input filters are not getting the updated controller
  service name, and ALSO need to be updated in the same fashion as
  REST/RPC entities
All URI service names are now normalized

- Added new listeners to Module class to ensure input_filter_name is
  also properly normalized and de-normalized.
- Added logic to REST/RPC resource class' `injectInputFilters()` logic
  to ensure that the controller service name is normalized for links,
  and that the input filter name is also normalized.
Fixes authorization screen

- Since the service name is derived from the parent service resource when
  building the permissions table, we need to normalize the service name to refer
  to the namespaced service names. Doing so makes the authorizations screen work
  as expected.
Normalize service name when creating docs permissions table

- Normalize the service name before we get the authorizations table for the
  current service -- `s/-/\\/g`.
Ensure service names are properly displayed on settings pages

- Created new filter, controllerservicename, which substitutes '\\' for '-' in
  the provided name.
- Updated servicename filter to look for either '-' or '\\' as a separator when
  creating names (I think this filter is likely unused at this point, however).
Rebuilt UI distribution
Merge branch 'hotfix/215'

Close #215
Fix an issue observed in Eclipse / Studio

With the 1.0.4 release of Apigility, you are no longer able to create a new API
via the Apigility interface in Eclipse. It fails silently.

On inspection, we determined that the POST request to create an API was being
sent as a GET request, for no apparent reason. We then started stepping through
commits from zf-apigility-admin's 1.0.2 tag up to the 1.0.3 tag to determine
when this behavior began. The commit that broke was 5c4087c, which was when
cache-control headers were committed. In examining the implementation,
commenting out the Last-Modified header resolved the issues observed in Studio.

Since Last-Modified is the weakest indicator in the set of cache control headers
used, we can safely remove it and still have reasonable expectations that the
cache control requests will be honored.
CS fixes (trailing whitespace)
Merge branch 'hotfix/eclipse-webkit-fix'

Close #224
Remove code marks from headings

- per zfcampus/apigility-documentation#40
Merge branch 'hotfix/readme-formatting'

Removes code markers from headings
Remove asset directory

- Split off into its own repo
Update configuration

- Add zf-apigility-admin-ui as a dependency
- Remove asset manager, view config
Remove UI artifacts

- Removed view script that moved to UI project
- Removed executable script that moved to UI project