Refactor raw api

The "raw" api on entries and uploads are refactored to use more consistent url paths, namely:

	Old		New
POST	/entries/raw/query	POST	/entries/rawdir/query
GET	/entries/raw	GET	/entries/rawdir
POST	/entries/raw/download/query	POST	/entries/raw/query
GET	/entries/raw/download	GET	/entries/raw
GET	/entries/{entry_id}/raw	GET	/entries/{entry_id}/rawdir
GET	/entries/{entry_id}/raw/download	GET	/entries/{entry_id}/raw
GET	/entries/{entry_id}/raw/download/{path}	GET	/entries/{entry_id}/raw/{path}
GET			/uploads/{upload_id}/rawdir/{path}
GET	/uploads/{upload_id}/raw/{path}	GET	/uploads/{upload_id}/raw/{path}
PUT	/uploads/{upload_id}/raw/{path}	PUT	/uploads/{upload_id}/raw/{path}
DELETE	/uploads/{upload_id}/raw/{path}	DELETE	/uploads/{upload_id}/raw/{path}

Further, the raw GET api method on upload is split into two distinct endpoints, one for downloading the directory/file data (raw), and one for getting the metadata (rawdir). The result is also paginated, and we add an argument include_entry_info.