apply-geolocation-rules: Rule matching should be case-insensitive

[joverlee521]

Context

I recently added an geolocation rule in nextstrain/avian-flu#121 that I was surprised was not already included in the "central" geolocation rules in ncov-ingest. While auditing the "central" rules for #1488, I realized that this was due to the different string casing of the rules.

North America/USA/Ca/* vs North America/USA/CA/*

The raw location matching should be case-insensitive so that we don't have to maintain rules for the different string casings.

Side note, my recent experience with fauna has made me wary of case-insensitive location matching, but it should be fine here because we do a hierarchical location match.

[jameshadfield]

👍 lowercase is what we use for geo matching in export too:

augur/augur/export_v2.py

Lines 512 to 520 in 73f1fa9

	for deme in trait_values: # note: deme may be numeric, or string
	try:
	deme_search_value = deme.lower()
	except AttributeError:
	deme_search_value = str(deme)
	try:
	deme_to_lat_longs[deme] = lat_long_mapping[(trait_info["key"].lower(), deme_search_value)]
	except KeyError:
	warn("{}->{} did not have an associated lat/long value (matching performed in lower case). Auspice won't be able to display this location.".format(trait_info["key"], deme))