replacing files with the custom reports listing
small formatting tweak
rename configs, and create new whilelist sample
Implement new Model, Plugin, and Whitelists
We are changing the model from Report to CustomReport, the plugin
name/folder form ReportManager to CustomReporting, and adding in
the new whitelisting format. These changes required some refactoring.

As part of the refactoring, we also moved much of the field management
functions and whitelisting/blacklisting functions into utility functions
within the controller. In future commits I'll likely move these to the
model, where they better belong.
Remove OneToMany options
We're going to revist the limitations put on one-to-many relationships
as part of this reporting plugin. As such, we are removing the logic
that is currently in place, as it allows for only a single one-to-many
relationship to be included.
update readme file
update readme file
update readme file
Initial commits to get reports displaying and ignoring the old OneToManyOptions
First pass of updated report saving
Alls us to save the details to the database. This doesn't address
loading or editing (that'll be a future commit), but it does successfully
enable saving to the database and deleting the reports.
Fix up report loading
fix running of reports
fix form submission for viewing reports
update setup instructions
Restore report editing, add report duplicating
Now when saving, we'll either add or update the existing report depending
on whether there is already an ID for the data.
I also added in the function to duplicate an existing report, which will make
a copy, but will prepend "Copy of" to the title.
Differentiate between "Load" and "View"
In the original version of the plugin, loading up an existing report would
simply push you into the wizard, which leads to unnecessary steps. I'm not
differentiating between "viewing" a report (which views the result) and "editing"
a report, which actually loads you into the wizard.

TODO: replace "load" method with a more intelligent "edit" so that it's
more like CakePHP pattern.
restore excel export functionality
remove oneToMany and manyToMany relationships
cleaning up CSS for reports
Replace load() with edit()
We already have an edit method that would accept form data to update
the stored report. By removing the load method, and having edit()
handling both the form loading and the saving, we're being more
consistent with other CakePHP conventions.