Corpus dashboard in angular

This is the first step towards getting functionality out of the prototype. in this pull request we have new directives in the angular_client/modules/core folder which are used in the new corpus dashboard in the angular_client/modules/corpuspages folder. 


![corpus_dashboard_underway](https://cloud.githubusercontent.com/assets/196199/2895665/ae6dd99c-d562-11e3-9e50-22c02da26839.png)

Directives now in core (FieldDB/angular_client/modules/core)
```bash
├── scripts
│   ├── app.js
│   ├── controllers
│   │   └── main.js
│   ├── directives
│   │   ├── fielddb-corpus-terms-of-use.js
│   │   ├── fielddb-corpus.js
│   │   ├── fielddb-offline-controls.js
│   │   ├── fielddb-search.js
│   │   └── fielddb-user.js
│   ├── private_services.js
│   └── services
│       └── servers.js
├── styles
│   └── main.css
└── views
    ├── core.html
    ├── corpus-page.html
    ├── corpus.html
    ├── data-page.html
    ├── offline-controls.html
    ├── search.html
    ├── terms-of-use.html
    ├── user-page.html
    └── user.html
```

here are its dependancies (bower components)

```
$ mkdir  $FIELDDB_HOME/FieldDB/angular_client/modules/core/app/bower_components/fielddb
$ ln -s   $FIELDDB_HOME/FieldDB/fielddb.js $FIELDDB_HOME/FieldDB/angular_client/modules/core/app/bower_components/fielddb/fielddb.js

$ ls app/bower_components/
angular			angular-mocks		angular-route		angular-scenario	es5-shim		jquery
angular-cookies		angular-resource	angular-sanitize	bootstrap		fielddb			json3
```


there are also numerous other changes ot the testing infrastructure etc. the new code uses grunt build to build the minified version, and bower install (or symlinks) to include components inside of other components. 


the corpuspages looks like this: (FieldDB/angular_client/modules/corpuspages)
```bash
├── scripts
│   ├── app.js
│   └── controllers
│       ├── corpus-page.js
│       ├── main.js
│       └── user-page.js
├── styles
│   ├── bootswatch_united.css
│   └── main.css
└── views
    └── main.html
```


here are its dependancies (bower components)

```
$ ls -al ../corpuspages/app/bower_components/
total 24
drwxr-xr-x  17 gina  staff  578 May  2 19:35 .
drwxr-xr-x  15 gina  staff  510 May  5 12:14 ..
drwxr-xr-x  10 gina  staff  340 Apr 23 23:32 angular
drwxr-xr-x   8 gina  staff  272 Apr 23 23:32 angular-cookies
drwxr-xr-x   6 gina  staff  204 Apr 23 23:32 angular-mocks
drwxr-xr-x   8 gina  staff  272 Apr 23 23:32 angular-resource
drwxr-xr-x   8 gina  staff  272 Apr 23 23:32 angular-route
drwxr-xr-x   8 gina  staff  272 Apr 23 23:32 angular-sanitize
drwxr-xr-x   8 gina  staff  272 Apr 23 23:32 angular-scenario
drwxr-xr-x  11 gina  staff  374 Apr 23 23:32 bootstrap
drwxr-xr-x  16 gina  staff  544 Apr 23 23:32 es5-shim
lrwxr-xr-x   1 gina  staff   50 Apr 24 10:19 fielddb-activity-feed -> /Users/username/fielddbhome/FieldDBActivityFeed/client
lrwxr-xr-x   1 gina  staff   59 May  1 17:23 fielddb-angular -> /Users/username/fielddbhome/FieldDB/angular_client/modules/core
lrwxr-xr-x   1 gina  staff   38 May  2 19:35 fielddb-lexicon-angular -> /Users/username/fielddbhome/FieldDBLexicon
drwxr-xr-x  17 gina  staff  578 Apr 24 09:07 fontawesome
drwxr-xr-x   7 gina  staff  238 Apr 23 23:32 jquery
drwxr-xr-x   7 gina  staff  238 Apr 23 23:32 json3
```

To be able to build the corpus pages you need to have these sym links set up (at the moment, becaseu these modules are not stable and deployed as bower packages), and you need to run "grunt build" in each of the projects to make sure they are built and can be included.