Don't bother with otm_code for migrations

Migrations will come with predetermined ITreeRegion codes, which should
be written into the migration as ITreeCodeOverride records.

Doing code searches is a second-best method for producing calculable
ecobenefits for species.

Only one of these methods should be used.
Bail out of migrations if species could conflict
Merge pull request #1619 from steventlamb/topic/fix_migrator_species_duplication

Topic/fix migrator species duplication
Update unit test to match change in species import
Fixes #1553, styling on comments
Fixes #1422, layout issues with checkboxes in add process
Fixes #1499, lightbox photo edit button weird styling
Fixes #1222, long field values spill out of wells
Fixes #930, species input should be wider
Cleanup UI properly after error

I observed that after a failure, the UI did not clean itself up
properly. Subsequent exports worked, but would continue to display the
earlier failure message.

I reworked the displayManager to be a little simpler as well.
Merge pull request #1620 from mtedeschi/topic/styling-improvements-comments

Styling improvements comments
Fix issues that arose in latest migration
Merge pull request #1622 from steventlamb/bug/migrator_issues

Fix issues that arose in latest migration
Add admin actions to comment moderation

This includes: hiding/unhiding, archiving/unarchiving, and unflagging.
Actions can happen on individual rows, or on multiple rows at once
Add UI tests for comment moderation admin actions
Merge pull request #1618 from maurizi/comment-moderation-actions

Comment moderation actions
Merge pull request #1621 from steventlamb/bug/export_ui_cleanup

Cleanup UI properly after error
Don't hard code instance names in tests
Mask details about comment when moderator hides
Merge pull request #1623 from steventlamb/topic/hidden_comment_ui

Mask details about comment when moderator hides