Consolidate behaviour of quarantine file uploads

Full story: https://www.pivotaltracker.com/story/show/42490007

TL;DR: File uploads now behave the same in all environments, i.e.
quarantine file storage is used everywhere. This also modifies the
behaviour of our uploaders such that the "path" methods reflect the
expected location for files on the filesystem whilst
simplifying and consolidating the configurarion of the uploads
behaviour.

Now that we are using quarantine file storage in all envs, files
uploaded in development will not be accessible in the browser until
they have been moved to the clean-uploads folder. We added the
development:fake_virus_scan rake task that copies files from
incoming-uploads to clean-uploads.
Tidy up upload access integration tests
Renamed clean_uploads_path to clean_uploads_root
QuarantineFileStorageSimulator no longer needed

Uploaded file storage now behaves the same in all environments, so
this magic is not necessary.
Add Whitehall.incoming_uploads_root
Move config out of CarrierWave and into Whitehall

Now both incoming and clean are configured in the same place and the
configuration is not coupled to carrierwave itself.
Remove unnecessary expand_path call from helper
test-quarantine is no longer used
Use a proper file lock for quarantine testing
Update test cleanup task to reflect new behaviour
Add addtional signposting of monkey-patch
Rake task to fake virus scan in development

Simply copies all incoming files to the clean folder, which is good
enough to simulate a successful virus scan.