Removed RealTimeCloud module

[jnioche]

and put regionmapping logic in realtime cloud

implements #164

The RealTime Cloud module was only used to provide the mappings between cloud region codes and ElectricityMaps ones. This can be obtained straight from the EM API and will have better coverage and precision.

[jnioche]

There are differences between the data we have in main and what we have in this PR

│ Zone │ Name │ Direct (gCO2/kWh) │ Lifecycle (gCO2/kWh) │
│ US-NW-BPAT │ Bonneville Power Administration │ 76.91 │ 106.65 │
│ US-NW-PACW │ PacifiCorp West │ 146.95 │ 194.17 │

PACW is nearly 2× higher than BPAT — this is definitely the source of your different results for Oregon workloads.

Which is correct?

The em-datacenters.json places the datacenter at lon=-119.7, lat=45.8, which is Boardman, OR — right on the Columbia River. That location sits within BPA's service territory (US-NW-BPAT), not PacifiCorp West (US-NW-PACW). AWS is also
well-known for sourcing renewable power through the Bonneville Power Administration in Oregon.

The old CSV (US-NW-BPAT) appears to be the more accurate attribution. The new em-datacenters.json entry looks like it has an error — US-NW-PACW covers eastern Oregon/Utah/Wyoming, not the Boardman area.

I will patch this for now and report to EM later.

[jnioche]

Zone key changed:

┌────────────┬───────────────────────────────────────────────┬────────────┐
│ Region │ Old CSV │ New JSON │
├────────────┼───────────────────────────────────────────────┼────────────┤
│ eu-north-1 │ ES (last write wins from the duplicate SE/ES) │ SE-SE3 │
├────────────┼───────────────────────────────────────────────┼────────────┤
│ us-west-2 │ US-NW-BPAT │ US-NW-PACW │
└────────────┴───────────────────────────────────────────────┴────────────┘

Regions in old CSV missing from new JSON:

┌───────────────┬──────────────┐
│ Region │ Old zone key │
├───────────────┼──────────────┤
│ us-gov-east-1 │ US-MIDA-PJM │
├───────────────┼──────────────┤
│ us-gov-west-1 │ US-NW-BPAT │
└───────────────┴──────────────┘