Target v1.3.3
Set Last-Modified header to allow for 304 responses
Use a constant Last-Modified time with cache_policy=persist

After all if the client is asking for persistance it doesn't make
sense to set a different Last-Modified for different incoming
requests (even if we don't expect any) ....
Revert "Use a constant Last-Modified time with cache_policy=persist"

This reverts commit 4b5899ff1aec8c6682585bd2789179da3eed40d2.

The reason is that setting Last-Modified to a remote date in the past
triggers early expiration of cache (as max-age will be reached sooner)
Take cache_buster value, if present, as a Last-Modified timestamp

This makes the Last-Modified header consistent across requests
using the same cache_buster (embedded in the token for multilayer
API).
Add --with-sqlapi-port switch
Add --environment switch to restrict output to given env
Add more timing in the profile, add useProfiler config variable

Default to useProfiler:true in staging and development
Add example of including profile in response log line
Upgrade windshaft to improve profiling
Add note about layergroup logging at creation

The change is due to Windshaft upgrade.
Closes #76
Fix URLS and repository, add contributors, change author

Author became Vizzuality and contributors are the actual committers
Fix contributors, use short form for author
Merge branch 'release/staging'