Some filenames aren't compatible with Azure Storage

[adammcmaster]

Azure storage has more restrictive rules on filenames than S3. In our case, it seems some files/directories have periods at the end of their names, which is not allowed. (The docs say to avoid it, but azcopy encounters a 403 error when it tries to PUT those files so they appear to be disallowed completely.)

Example failing request: PUT https://zooniversestatic.blob.core.windows.net/$web/talk.chicagowildlifewatch.org/users/Salma_S./comments.html

Affected sites so far:

• radiotalk.galaxyzoo.org/
• talk.chicagowildlifewatch.org/
• talk.diskdetective.org/
• talk.galaxyzoo.org/
• talk.planethunters.org/
• talk.snapshotserengeti.org/
• talk.wormwatchlab.org/

See also Slack discussion. Summary:

• We will need to rewrite these filenames and rebuild (or compile a full list of affected files and rename them on S3, whichever all be quickest).
• @camallen suggests that we set up an Nginx rewrite rule to avoid breaking existing links.

[camallen]

one option to avoid a rebuild of all these sites is to manually rename all impacted paths for each site in s3. We would then provide the nginx URL rewrite via static server and copy the files over via azcopy

[camallen]

closed by #85 i've manually run the remap scripts and our nginx proxy now serves the invalid char URLs from the remapped files via https://github.com/zooniverse/static/pull/179