Update semicolon separator

[TheAdventurer64]

Problem 1: So, currently, presets for tags like brewery=*, Go Map!! uses a shows a semicolon separator for tags like brewery=yes;various. . This is problematic, as there are already the preset tags Yes and Various, so there shouldn’t be Yes;Various.

Problem 2: Currently, Go Map renders the semicolon separator on the editing screen like this: I think this is problematic for a few reasons:

1. People that are new to OpenStreetMap and mainly use the iD editor might not know how the semicolon separator works, as the editor automatically divides the tags for the user.

2. Having users manually type in the semicolon separator can lead to problems like this: As you can see here, the user can incorrectly space the two cuisine tags apart, so instead of the tag rendering as steak_house;coffee_shop, OpenStreetMap will render the tag as steak_house; coffee_shop which is incorrect, and may confuse data consumers.

To solve this, I propose that the editor renders the semicolon separator like this: (Note that instead of the down row like sequence, I think it would be better if the separator did a one line sequence, similar to iD.)

[GA-Kevin-Codes]

Just to piggy-back off this, I recently was showing a non-OSM user my hobby and we did a survey together. We had fun finding all the info for the cafe we went to, until we reached the cuisine tab. She was happy to select from a list multiple categories that the cafe would serve but was immediately confused by the overriding of previous choices and the semicolon delimitation. I had to manually write that tag in for her. iOS has a list picker where you can choose multiple options. Even if it's eventually displayed as semicolons (or nicer like the mockup above) the initial entry should be updated. Perhaps cuisine isn't the only tag to suffer this.