often, artists on MusicBrainz get tagged with the city of origin rather than just the country. this changes the API responses slightly, and it appears that the country field is omitted from these artists.
case in point: https://musicbrainz.org/ws/2/artist/416a8fc2-076b-4d9f-b972-a067e6b80e04
compare with an artist whose area is defined as a country: https://musicbrainz.org/ws/2/artist/c24d285d-1397-42c1-8372-65724294ecfa
fmbot appears to only look at the country field in API responses (https://github.com/fmbot-discord/fmbot/blob/dev/src/FMBot.Bot/Services/MusicBrainzService.cs#L46).
this makes commands such as .from or .countries (needlessly?) inaccurate.
i believe there is a relatively simple way to use the MusicBrainz API responses we're already requesting, to do a tiny bit more to search for the correct country and improve the accuracy of the aforementioned commands.
i would like to suggest that we first look for a non-null field at (excuse the notation) area.iso-3166-2-code-list.iso-3166-2-code, split by - and take the first element to get the country code.
https://en.wikipedia.org/wiki/ISO_3166-2 states that
The first part is the ISO 3166-1 alpha-2 code of the country;
so i believe this should be relatively safe to grab in the case of a non-null field, and that it'll always be a valid iso 3166-1 code which is what we desire.
if this field doesn't exist, one can fall back to country as we do today (there's also a field named area.iso-3166-1-code-list.iso-3166-1-code, but i think this is only set when country is also set, making it redundant).
one aspect i haven't thought of here is if there's any area in the MusicBrainz database with multiple iso 3166-2 codes. i've got the impression that such a location makes little sense, but it would be interesting to see if anyone's got an example of that occurring