chore!: renaming country to geoZone and zone to worldRegion

[cedricr]

🔧 Problem

Fixes #1532

See also: MTES-MCT/ecobalyse-data#179

[n1k0]

These are just preliminary remarks with the geoZone name, which could just be geozone and solves a lot of headaches wrt naming conventions across codebases. worldRegion could also be just region imho, but I won't die on this other hill. More broadly, even if I understand we can't use a same single concept and type for "any scale geographic location", I fear the two names — geo zone and world region — might be quite confusing to end-users and documentation readers… though I don't have much better suggestions to offer. What would prevent us to use a single concept and type? (I'm asking the question because I didn't spend the necessary time to investigate the matter yet am offering others to chime in, and I'm definitely part of the ones who should be involved answering that question)

[n1k0]

Same, I could live with just geozones just totally fine.

[cedricr]

These are just preliminary remarks with the geoZone name, which could just be geozone and solves a lot of headaches wrt naming conventions across codebases. worldRegion could also be just region imho, but I won't die on this other hill. More broadly, even if I understand we can't use a same single concept and type for the concept of "geographic location information", I fear the two names — geo zone and world region — might be quite confusing to end-users and documentation readers… though I don't have much better suggestions to offer. What would prevent us to use a single concept and type? (I'm asking the question because I didn't spend the necessary time to investigate the matter yet am offering others to chime in, and I'm definitely part of the ones who should be involved answering that question)

@n1k0 I’m even wondering if the 'geo' part is necessary after all… Couldn’t we go with just zone? @paulboosz what do you think ?

About worldRegions (previously named zones 😅). I’m afraid just “regions” would be more confusing, as you have administrative regions, of different levels, geopolitical regions, etc. I think “world region” has the advantage of evoking something “big” at least.
We could try something like "SuperZone", or “MetaZone” to be super clear that’s it a division above the Zone, but I’m not a big fan of the hyberbole.

That won’t be the end of the road, in the codebase, we also have “locations”, with their own semantic, coming from Brightway, “geographicOrigin”, with its own classification, “defaultOrigin”, with another classification, and probably others ? Baby steps… 😆