Tidying up loose ends in Event Application triaging

[olasitarska]

• Latitude & longtitude of the city/country needs to be fetched from the API when EventApplication is created (in save method?)
• @asendecka Logic for copying old event data if the event is an n-th event in given city
• @olasitarska Connect creating / changing email accounts in create_event ([WIP] Google Apps integrated into new event deploy logic #360)
• @asendecka Removing old organizers if the event is an n-th event in given city
• Sending acceptance email with confirmation link
• Confirmation page that changes status to DEPLOYED and carries on create_event actions (template for this already exist here
• Improve test coverage
• Coorganizers in application form
• Choosing a random picture when creating an event for the homepage
• Submitting the organizer form should send an email

Refactoring bits:

• Moving add_default_content and menu out of Event
• Moving create_event method from EventApplication
• Moving add_organizers from Event model
• Remove hardcoded "accepted" and "rejected" values from confirmation pages in admin triaging in templates

[olasitarska]

Google Apps in progress: #360

[asendecka]

Cloning event done in #369

[olasitarska]

Google Apps done in #375

[olasitarska]

Coordinates in #385

[olasitarska]

I think "@asendecka Removing old organizers if the event is an n-th event in given city" is actually not necessary, as I just checked and organizers are currently not copied when event is copied.