CRM-14159 API Add generic options['metadata'] = labels functionality

----------------------------------------
* CRM-14159: Add ability to return labels as top level metadata
  http://issues.civicrm.org/jira/browse/CRM-14159
CRM-14137 alter report metadata in api result to be keyed as 'metadata' per discussions

----------------------------------------
* CRM-14137: Report_template.getrows api - allow retrieval of metadata at the top level
  http://issues.civicrm.org/jira/browse/CRM-14137
Fix e-notice on Case/Demographics report so it does not need to be excluded from test
CRM-13889 - api_v3_DashboardContact - Fix validation

The validation of dashboard_id implicitly involved a permission-check. This
permission-check would be wrong in some cases (eg running a drush script
without any particular user), but it could be right in other cases (eg
issuing an AJAX call).
CRM-14091. Look for obvious misconfigurations and warn.
CRM-14091. Run checks at most once a day for each user with administrative permissions.
Account for differing path structures in different CMS backends.
CRM-14092. Generate blank index.html files in public directories.

Conflicts:
	CRM/Utils/Check/Security.php
CRM_Utils_Check_Security - Change case of function names
CRM_Utils_Check_Security - Make getFilePathMarker non-static

If we write tests for this, it will be harder to run with different markers
if the function is static.
CRM_Utils_Check_Security - Split allChecks in two:

 * checkAll - Simply aggregates the other checks
 * showPeriodicAlerts - Application logic for when/how to run check
CRM_Utils_Check_Security - Remove hard dependency on CRM_Core_Session::setStatus
code/comment cleanup
test cleanup
Merge pull request #2454 from eileenmcnaughton/CRM-14159

CRM-14159 API Add generic options['metadata'] = labels functionality
More consistently restrict access to template, config/log, and upload dirs.
CRM_Utils_Check_Security - Autoformat
CRM-14091 - Change URLs for doc links

----------------------------------------
* CRM-14091:
  http://issues.civicrm.org/jira/browse/CRM-14091
Revert "CRM-14169 - require access CiviCRM permission in addtion to access CiviEvent permission in order to create a new event and in order to access Manage Events page (event/manage path)."

This reverts commit be87f5a989291fc7f2d5f247daa26375664bb9ec.
CRM-14169 - Reverted the change to require access CiviCRM since creating an event does work for auth user with access CiviEvent and there are use cases for this. We will add a config warning separately if inappropriate perms have been granted to anonymous users. Removed access CiviCRM requirement from ajax.locBlock since that breaks the Location tab in events for users who can otherwise properly create an event.

----------------------------------------
* CRM-14169:
  http://issues.civicrm.org/jira/browse/CRM-14169