feat: Populate searchableLocationName with event location:

[abhinavk96]

Fixes #3149

Short description of what this resolves:

Ensures that searchableLocationName is populated, when event location is being saved. The data from this field will be later used to list the most common cities.

[prateekj117]

@CosmicCoder96 This solution would work for new locations, what about the already saved locations?

[abhinavk96]

All legacy data already has searchable locations defined in database. Which leaves 10-20 new events without it. We’ll live with it. Or we can just save their location again through the wizard it will reflect it then.

…

On Mon, 17 Jun 2019 at 1:02 PM, Prateek Jain ***@***.***> wrote: @CosmicCoder96 <https://github.com/CosmicCoder96> This solution would work for new locations, what about the already saved locations? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3150?email_source=notifications&email_token=AEDUDRN7CMQ7HLD352PM7A3P24LHJA5CNFSM4HYR5VM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX2BJMY#issuecomment-502535347>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEDUDRLMGE6HPYRY5SNAB7DP24LHJANCNFSM4HYR5VMQ> .

[mariobehling]

Yes, we can just re-run the wizard. Thanks. Let's merge this.