Refactor ecobenefits views to avoid decorators

Similar to the treemap app, eco benefits now follows a schema
similar to:

```python
def benefits_for_tree(instance, tree_id):
    return ...

benefits_for_tree_view = json_api_call(
    instance_req(strip_req(benefits_for_tree)))
```
Add numpy for the eco.py library
Add tests for Species.scientific_name
Merge pull request #79 from ahinz/topic/eco-views

Refactor ecobenefits views to avoid decorators
Refactor tests for clarity
Merge pull request #83 from maurizi/topic/testSpeciesScientificName

Add tests for Species.scientific_name
Initial API import from OTM1 (broken)
Add api app to OTM2
Remove compiler issues and warnings from tests

Baseline 'api.Version' is working

Also upgrade to Django 1.5 best practices
Create initial api shims in treemap views
Refactor api recent edits to work with audits
OTM2 searching and tiling have changed, remove the old stuff

In particular, the API no longer supports generating tiles,
nor does it support the old filtering style (including CQL).

OTM2 api-based apps should instead use Windshaft TMS with a
standard OTM2 json-based filter query string.
Tree photos aren't implemented yet, so add shim and remove test
Refactor plot distance search to use standard filter syntax
Use ecobenefit benefit calculation apis
Update user and species dict converters

We may want to move this sort of thing out to the models at some point
Update geocoder- add TODOs for later
Use shim methods in treemap.views to support API tests

OTM2 doesn't support creating and validating plots yet, so in an
effort to get the tests to pass from the API's point of view some
random functionality was included (particularly, the 'create_plot'
funtion)
Update pending system to use new audit based pends
Use standard audit system for deletion