Create migration script for theme 2.0

[mattstratton]

This will be a long-running issue, but it needs to be captured. Need to update this ongoing with requirements, etc.

[mattstratton]

The tool used for this is located at devopsdays/migrator.

Note that this is kind of how the migration works (just to keep track):

• The source is ~/src/github.com/devopsdays/devopsdays-web on branch master (pull from origin before running migration)
• The destination is ~/src/migrate/devopsdays-web (create a new branch off of development before migrating; this is the source for the updated theme code as well, which should be merged into development branch prior to migrating, etc)
• "Old" content files are located at ~/src/dod-backup
• Copy the content directory from ~/src/dod-backup to ~/src/github.com/devopsdays/devopsdays-web prior to migration
• In theory, the data/speakers/yyyy directories are already up to date in ~/src/github.com/devopsdays/devopsdays-web
• Run the "migrate sponsors" command in migrator to migrate all sponsor data from the source to the destination directories
• Run the "migrate events" command in migrator to migrate all events from the source to the destination directories
• Test the build time with the "full" amount of events (static migrated to non-static)
• Optional: After the test, if things look clean, need to do some cleanup in the static directory to remove all the HTML output. This has to be done manually.

One random note; might have to do the "static directory cleanup" stuff prior to running the test, as hugo might not try to generate/process content files if the static directory already exists?